Exceed Persistent Connection Limit on a ServicePoint?

How can I exceed the number of persistent connections allowed on a
ServicePoint(which is 2 connections)? I believe this is the cause of the
problems with my thread from earlier titled "Unable to write data to the
transport connection & Timeout". After looking at the database, it appears
there are time overlaps(from when a connection goes out to when it comes
back), and during these overlaps is when I receive the timeout messages.

I have tried setting ServicePointManager.DefaultConnectionLimit to a higher
value, but that seems to have no effect. If there is no way to raise the
limit, how can I work around it? This is increasingly becoming a problem as
the site grows and there is more and more traffic.

Thanks,
Steve

re: Exceed Persistent Connection Limit on a ServicePoint?

Have you tried editing your machine's Machine.config
settings? In the system.net node under
connectionManagement there is a maxconnection attribute.
The default is set to 2. Try increasing the number and see
that fixes the problem.[color=blue]
>-----Original Message-----
>How can I exceed the number of persistent connections[/color]
allowed on a[color=blue]
>ServicePoint(which is 2 connections)? I believe this is[/color]
the cause of the[color=blue]
>problems with my thread from earlier titled "Unable to[/color]
write data to the[color=blue]
>transport connection & Timeout". After looking at the[/color]
database, it appears[color=blue]
>there are time overlaps(from when a connection goes out[/color]
to when it comes[color=blue]
>back), and during these overlaps is when I receive the[/color]
timeout messages.[color=blue]
>
>I have tried setting[/color]
ServicePointManager.DefaultConnectionLimit to a higher[color=blue]
>value, but that seems to have no effect. If there is no[/color]
way to raise the[color=blue]
>limit, how can I work around it? This is increasingly[/color]
becoming a problem as[color=blue]
>the site grows and there is more and more traffic.
>
>Thanks,
>Steve
>
>
>.
>[/color]

re: Exceed Persistent Connection Limit on a ServicePoint?

Nope, this didn't seem to have any effect. Any other ideas?

Thanks,
Steve

"Cole Breidenbach" <cybreid2000@yahoo.com> wrote in message
news:0ac501c394f4$18998070$a001280a@phx.gbl...[color=blue]
> Have you tried editing your machine's Machine.config
> settings? In the system.net node under
> connectionManagement there is a maxconnection attribute.
> The default is set to 2. Try increasing the number and see
> that fixes the problem.[color=green]
> >-----Original Message-----
> >How can I exceed the number of persistent connections[/color]
> allowed on a[color=green]
> >ServicePoint(which is 2 connections)? I believe this is[/color]
> the cause of the[color=green]
> >problems with my thread from earlier titled "Unable to[/color]
> write data to the[color=green]
> >transport connection & Timeout". After looking at the[/color]
> database, it appears[color=green]
> >there are time overlaps(from when a connection goes out[/color]
> to when it comes[color=green]
> >back), and during these overlaps is when I receive the[/color]
> timeout messages.[color=green]
> >
> >I have tried setting[/color]
> ServicePointManager.DefaultConnectionLimit to a higher[color=green]
> >value, but that seems to have no effect. If there is no[/color]
> way to raise the[color=green]
> >limit, how can I work around it? This is increasingly[/color]
> becoming a problem as[color=green]
> >the site grows and there is more and more traffic.
> >
> >Thanks,
> >Steve
> >
> >
> >.
> >[/color][/color]

re: Exceed Persistent Connection Limit on a ServicePoint?

Sorry to hear the Machine.config edit didn't work. Amazing
how the obvious setting change doesn't work all the time.
Well, the only other thing I can think of is the
limitation in the WinInet library that the .Net Framework
may be using for client HTTP connections. Here is a
knowledge base article for your review.

http://support.microsoft.com/default...id=kb%3Ben-us%
3B183110

Good luck.
[color=blue]
>-----Original Message-----
>Nope, this didn't seem to have any effect. Any other[/color]
ideas?[color=blue]
>
>Thanks,
>Steve
>
>"Cole Breidenbach" <cybreid2000@yahoo.com> wrote in[/color]
message[color=blue]
>news:0ac501c394f4$18998070$a001280a@phx.gbl...[color=green]
>> Have you tried editing your machine's Machine.config
>> settings? In the system.net node under
>> connectionManagement there is a maxconnection attribute.
>> The default is set to 2. Try increasing the number and[/color][/color]
see[color=blue][color=green]
>> that fixes the problem.[color=darkred]
>> >-----Original Message-----
>> >How can I exceed the number of persistent connections[/color]
>> allowed on a[color=darkred]
>> >ServicePoint(which is 2 connections)? I believe this is[/color]
>> the cause of the[color=darkred]
>> >problems with my thread from earlier titled "Unable to[/color]
>> write data to the[color=darkred]
>> >transport connection & Timeout". After looking at the[/color]
>> database, it appears[color=darkred]
>> >there are time overlaps(from when a connection goes out[/color]
>> to when it comes[color=darkred]
>> >back), and during these overlaps is when I receive the[/color]
>> timeout messages.[color=darkred]
>> >
>> >I have tried setting[/color]
>> ServicePointManager.DefaultConnectionLimit to a higher[color=darkred]
>> >value, but that seems to have no effect. If there is no[/color]
>> way to raise the[color=darkred]
>> >limit, how can I work around it? This is increasingly[/color]
>> becoming a problem as[color=darkred]
>> >the site grows and there is more and more traffic.
>> >
>> >Thanks,
>> >Steve
>> >
>> >
>> >.
>> >[/color][/color]
>
>
>.
>[/color]

re: Exceed Persistent Connection Limit on a ServicePoint?

I was under the impression that the .Net Framework did not make use of the
WinInet library. Is this not the case?

Thanks

"Cole Breidenbach" <cybreid2000@yahoo.com> wrote in message
news:00f001c39723$e05cbf10$a301280a@phx.gbl...[color=blue]
> Sorry to hear the Machine.config edit didn't work. Amazing
> how the obvious setting change doesn't work all the time.
> Well, the only other thing I can think of is the
> limitation in the WinInet library that the .Net Framework
> may be using for client HTTP connections. Here is a
> knowledge base article for your review.
>
> http://support.microsoft.com/default...id=kb%3Ben-us%
> 3B183110[/color]

re: Exceed Persistent Connection Limit on a ServicePoint?

I'm not exactly sure what win32 api's are used for network
communication for .Net. Or, if .Net even uses the WinInet
api's. However, I know that 2 connections is the HTTP 1.1
protocal standard per HTTP specification. And since the
problem at hand is no more than two connections, I thought
maybe the default connection limit for WinInet could be
adjusted in the registry. There is no dought I could be
wrong on this one. But give it a try and see what happens.


[color=blue]
>-----Original Message-----
>I was under the impression that the .Net Framework did[/color]
not make use of the[color=blue]
>WinInet library. Is this not the case?
>
>Thanks
>
>"Cole Breidenbach" <cybreid2000@yahoo.com> wrote in[/color]
message[color=blue]
>news:00f001c39723$e05cbf10$a301280a@phx.gbl...[color=green]
>> Sorry to hear the Machine.config edit didn't work.[/color][/color]
Amazing[color=blue][color=green]
>> how the obvious setting change doesn't work all the[/color][/color]
time.[color=blue][color=green]
>> Well, the only other thing I can think of is the
>> limitation in the WinInet library that the .Net[/color][/color]
Framework[color=blue][color=green]
>> may be using for client HTTP connections. Here is a
>> knowledge base article for your review.
>>
>> http://support.microsoft.com/default.aspx?scid=kb%3Ben-[/color][/color]
us%[color=blue][color=green]
>> 3B183110[/color]
>
>
>
>.
>[/color]