Exceed Persistent Connection Limit on a ServicePoint?

  • Thread starter Thread starter Steve - DND
  • Start date Start date
S

Steve - DND

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
 
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.
-----Original Message-----
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
Click to expand...
ServicePointManager.DefaultConnectionLimit to a higher
 
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.aspx?scid=kb;en-us%
3B183110

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

Thanks
 
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.
 
Back
Top