Bugzilla – Full Text Bug Listing
| Summary: | Update Kills Internet Connection | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Robin Corps <robin> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | francois, mariuszs, matt.doran, tmulle |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Robin Corps
In my search of a solution I came across one other person who was experiencing this bug, however there was no proposed solution. This was found here: http://dev.eclipse.org/mhonarc/lists/platform-dev/msg00629.html I'm experiencing the same thing. I think this bug might be related to bug 79212. I'm using Eclipse on Windows XP with SP2 and my Internet connection is via a US Robotics router. I haven't tested using the feature update (org.eclipse) on my linux laptop yet. Perhaps that's something I could try. Strangely, the same update worked on my machine at work, where there's a proxy. I was trying to get WTP via update, but it killed my Internet connection every time, so I had to get the zip files manually. I think this needs to be looked at promptly. I've spoken to some co-workers of mine and they could never use the feature update successfully, either. Kills more than internet connection - kills entire network connection, but I cannot reproduce it across multiple machines. Where it is reproducible, it is always reproducible. My test: 1. at command line, ping -t www.google.com 2. open Explorer at a local network share 3. open Internet Explorer or Firefox at eclipse.org 4. run nslookup www.google.com 5. run ipconfig The start Eclipse update, choose any update and start the download. When the download or verification 'stalls', switch to the other windows and see that 1. pings timeout, 2. Windows complains about unable to contact, 3. a refresh times out, 4. a name lookup times out, 5. often ipconfig will report either no IP address or an automatic IP address (XP not DHCP) Press Cancel on the update and wait a very long time; when update cancels, close Eclipse. Re-check all the other apps - the network is fine. Sometimes it fails during long downloads, sometimes during verification - I think it may be time based rather than activity based but not sure. I have re-installed multiple times, but I think I probably haven't completely cleared out the previous installation. Im using Eclipse 3.1.2 in local network, connection is made with D-Link WIFI, Windows XP. When I try to use update manager, after downloading package, when eclipse try to validate packages connection to internet is dead. Now is impossible to use update manager to install WTP 1.0.1 and new ECF. Please make full package download for WTP 1.0.1. Im using eclipse 3.1.2 in home too, but in network without WIFI and update manger works very good for me. Maybe this error is related to WIFI connections? I too am experiencing the same thing. My internet connection is killed at random times when downloading any updates, causing me to have to close eclipse and restart the update process. I'm running on Windows XP SP2, with Linksys WRT54G router and Linkysys Wifi card and WPA encryption turned on. I don't have any problems downloading with other programs. (In reply to comment #5) > Im using eclipse 3.1.2 in home too, but in network without WIFI and update > manger works very good for me. Maybe this error is related to WIFI connections? > (In reply to comment #5) > Im using eclipse 3.1.2 in home too, but in network without WIFI and update > manger works very good for me. Maybe this error is related to WIFI connections? > I am on WinXP SP2, hard wired into a D-Link 614 router, and am experiencing this exact problem. Once it halts, the network connection on the computer simply stalls... no incoming/outgoing traffic on the adaptor at all until eclipse wakes up, or I kill the javaw process. Same problem here... this is actually the same problem as bugs bug 79212, bug 74382 and bug 103776 it seems... Looks like there is a constant here : WinXP SP2... I have VNCed in a buddy on IRC that had that problem two days ago on 3.2M6 He could reproduce that bug very consistently when trying to update EMF. I witnessed it, despite I never experienced it myself. Intesrestingly enough the crash was occuring very reliably at the exatct same stage in the update process. Philippe, could you please check the hardware configuration of your buddy? Have you run with a tcp monitor (sysinternals.com) and see if the connections ever time out? In previosu bug report I have attached a patch that was trying to close streams (and hopefully connection) you may want to try it. I also just encountered this and have had this problem many times in the past. It's extremely annoying, and basically means you can't update eclipse ... and all your other network connections die. I'm pretty sure this relates to the XP SP2 connection throttling "feature", designed to stop people using Windows for denial of service attacks. You will probably find an event log entry under system with Event ID: 4226 and description "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts." I get this entry after trying to do Eclipse updates. Apparently the limit is imposed on the number connections initiated per second. My update fails during the "verification" phase, and eclipse is holding many connections open to the update site. Once the MS limit is reached everything hangs. I think the update manage needs to be much more careful about the number of connections it opens. Maybe use keep alive connections? Maybe explicitly close connections that it doesn't use? Maybe add a delay between each new connection to the update site? Since this is happening only on xp sp2 it might be because of this: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx quote: “Limited number of simultaneous incomplete outbound TCP connection attempts Detailed description The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue and will be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting will occur. When it does occur, a new event, with ID 4226, appears in the system’s event log. Why is this change important? What threats does it help mitigate? This change helps to limit the speed at which malicious programs, such as viruses and worms, spread to uninfected computers. Malicious programs often attempt to reach uninfected computers by opening simultaneous connections to random IP addresses. Most of these random addresses result in a failed connection, so a burst of such activity on a computer is a signal that it may have been infected by a malicious program.” However this limit is 10 as far as I know and we should not approach this number. On top of that all that should happen in this case is that eclipse should be slowed down by xp, but you never know. We have one sp2 machine for testing and we can not reproduce this problem on it. However, I found this http://geekswithblogs.net/tpatel/archive/2004/07/26/8849.aspx and this http://www.msfn.org/comments.php?shownews=9017 maybe this will solve your problems. Can you please try one of this workarounds. tested on several xp sp2 machines and could not reproduce. changing this to major. (In reply to comment #13) > tested on several xp sp2 machines and could not reproduce. changing this to > major. > This is not always visible, Try to install new Spring IDE 1.3 with update site. I have this error: Unable to complete action for feature "Spring IDE" due to errors. Unable to retrieve remote reference "http://springide.org/updatesite/plugins/org.springframework.ide.eclipse.ui_1.3.0.jar". [No route to host: connect] Unable to retrieve remote reference "http://springide.org/updatesite/plugins/org.springframework.ide.eclipse.ui_1.3.0.jar". [No route to host: connect] Network connections is dead. I try to set: "TcpNumConnections"=dword:00fffffe and install patch: EvID4226Patch223d-en.zip without success. This error always exists, Tested on two win xpsp2. This errors exists for me only when Im using WIFI connections, to install something via update manager I need use wired connection. Strange is, when I run update manager all files are downloaded OK, but when eclipse try to install files, then try download files again and network connections is dead. I had the same. The files downloaded OK, but all the connections died during the verification phase. But other times the download has also failed ... I think when it was checking the mirror sites? This happens when I'm on a LAN ... but I'm in Australia, so maybe it only occurs when connections to the update sites are slow?? The IBM guys might not be able to replicate if they have a fast connection to the sites. This is a duplicate of bug 101575. please check comment 33. thanks *** This bug has been marked as a duplicate of 101575 *** I dont have problems any more with update manager (eclipse 3.2rc7, winxp, jdk1.5.07) |