Re(2): Nonlinear limits on the number or rate of NSURLConnections
Re(2): Nonlinear limits on the number or rate of NSURLConnections
- Subject: Re(2): Nonlinear limits on the number or rate of NSURLConnections
- From: Peter Lovell <email@hidden>
- Date: Thu, 27 Aug 2009 10:33:24 -0400
On Wed, Aug 26, 2009, Jerry Krinock <email@hidden> wrote:
>It's an old Apple "Dual Ethernet" Airport, the same one that I had in
>2005 when I did not see this behavior. Of course, its firmware has
>probably been updated a couple times since then, now 4.0.9. I just
>looked through its configuration and definitely there are no settings
>regarding throttling or denial-of-service. Unless someone can confirm
>that this unit cannot be responsible, I guess I'll have to bypass it
>to be sure.
Hi Jerry,
I seem to remember that TCP stays in TIMED WAIT for 2 MSLs (max segment
lifetime) after the connection is closed. This prevents a stray segment
from an old connection interfering with a new connection. So something
has to keep track of that state somewhere.
You said that you had lots of sockets so I guess that's not the problem.
But maybe some device upstream is running out? A NAT router perhaps?
Then the question becomes - why is it different now?
Regards.....Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden