| Use of P2 update manager causes all TCP/IP connections to fail [message #121266] |
Mon, 17 November 2008 15:39  |
Eclipse User |
|
|
|
I know this will sound like a strange problem, and I agree that no real
OS would let this happen, but alas I do not have control of all such things:
On my Windows XP laptop, whenever I run Eclipse Update or Install, when
it connects to the update sites, I loose all TCP/IP connectivity right
after. My IM clients stop, I can't load any webpages. It usually comes
back after 1 or 2 minutes, but I've found it is much faster to just
enable / disable the network card. In fact, I usually have to disable,
then reenable my network card in between the P2 update manager license
question and pressing the "Install" button if I want the update to work.
It has happened with both 3.4 and 3.4 SR1. It really drives me nuts --
I can not imagine how running update in any user level program could
cause all TCP/IP connections to drop -- yet it does.
My os is XP, SP3, with the standard Norton antivirus and firewalls.
I've tried replicating with the firewall disabled, but get the same
results.
Has anyone else seen this before? Is there any known solution?
Thanks
Greg
|
|
|
| Re: Use of P2 update manager causes all TCP/IP connections to fail [message #121313 is a reply to message #121266] |
Wed, 19 November 2008 16:04  |
| Eclipse User |
|
|
|
There is a problem with Windows TCP/IP when opening a lot of ports in a
short time.
This problem is caused by a lack of reusable sockets, since each TCP/IP
connection stays in the TIME_WAIT state when the connection is being closed.
While a connection is in that state, the socket can't be reused and the
application can use up all available ports before the ports can be recycled.
MS Windows has 2 registry parameters (placed at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\P arameters)
that define this behavior :
- MaxUserPort (default 5000) - define the maximum number of ports that
can be open.
- TcpTimedWaitDelay (default 120 sec) - this parameter determines the
length of the time that a connection stays in the TIME_WAIT when it is
being closed.
Reducing this value from its default setting of 120 seconds will make
ports available sooner.
I recommend to change MaxUserPort to 65534 and TcpTimedWaitDelay to 30 sec.
Snjeza
Greg Smith wrote:
>
> I know this will sound like a strange problem, and I agree that no real
> OS would let this happen, but alas I do not have control of all such
> things:
>
>
> On my Windows XP laptop, whenever I run Eclipse Update or Install, when
> it connects to the update sites, I loose all TCP/IP connectivity right
> after. My IM clients stop, I can't load any webpages. It usually comes
> back after 1 or 2 minutes, but I've found it is much faster to just
> enable / disable the network card. In fact, I usually have to disable,
> then reenable my network card in between the P2 update manager license
> question and pressing the "Install" button if I want the update to work.
>
> It has happened with both 3.4 and 3.4 SR1. It really drives me nuts --
> I can not imagine how running update in any user level program could
> cause all TCP/IP connections to drop -- yet it does.
>
> My os is XP, SP3, with the standard Norton antivirus and firewalls. I've
> tried replicating with the firewall disabled, but get the same results.
>
> Has anyone else seen this before? Is there any known solution?
>
> Thanks
> Greg
|
|
|
Powered by
FUDForum. Page generated in 0.07739 seconds
Home