Community
Participate
Working Groups
Sorry for the awkward and vague bug summary, but I have really no idea what's going on here. I'm trying to install the CDT 2.1.1 through the software update facility in Eclipse (Help::Software Updates::Find And Install...). Every single time I try, at some point during the downloads the update will freeze, because the whole Windows network stack has just stopped responding. I'm not even able to ping by ip another machine on the lan. The only way I can get the networking back is by unplugging & replugging the network cable. I was able to install a smaller package (PyDev) so maybe this is related to the size of the download. The update site url I used for CDT: http://download.eclipse.org/tools/cdt/releases/new My current version is the one that comes with the bundle for the 1.0M4 WTP milestone (wtp-eclipse-emf-gef-jem-sdk-1.0M4.zip on the WTP downloads page). I believe the corresponding Eclipse version is 3.1M6. The build id says I20050401-1645. My java runtime version is 1.5.0_02-b09. The problem doesn't occur in Eclipse 3.0. I was able to reproduce this systematically on 2 completely separate networks, with 3 different machines. 2 of those ran Win2K (SP4), the other WinXP (SP2).
Vincent, if possible, please use the latest RC4 build, it has one fix that deals with connection problems, particularly when things fail. Your use cases may benefit from it. Thanks.
I can't find a link to the RC4 build (the latest is RC3 on the homepage). Where is it?
Not done yet. Try the 8pm I build when it is ready.
Ok, I just tried RC4, the same thing happens.
I've reproduced the bug again with the 3.1 release. Can anybody else reproduce this?
I have also the same problem, but it seems that it does not depend on the download size. I tried to install JBossIDE (http://jboss.sourceforge.net/jbosside/updates), size about 14MB: the download was successful, but during the verifying process the network stack stopped responding. I got the network back by exiting Eclipse. Eclipse 3.1 I20050627-1435 Java Runtime 1.5.0_04-b05 Windows 2k(SP4)
I am experiencing the same problem... After attempting to install using the install/update tool my network connection hangs until I exit eclipse and re- enter or eventually once the install/update times out and fails, I will get intermitent network connection restored. Terminating eclipse immediately restores network operation. Eclipse 3.1 eclipse.buildId=I20050627-1435 Sun 1.5.0_03 Windows XP SP1
I've also experienced the problem. It's been occurring through all releases of 3.x A work-around is downloading manually and unzipping features to the eclipse directory, but unfortunately this seem not to result in the the exact same configuration (not same versions of features available, for example the VE-editor 1.0.1 isn't available on the download site). For me the freeze of the network stack occur 95% of the time I download a plugin, pretty much regardless of size. I also tried closing the personal firewall (ZoneAlarm), but that didn't change anything. My specs: Athlon XP 3000 1 Gig PC2700 RAM Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller WinXP Pro SP2 Eclipse 3.1.0 Build id: I20050627-1435 PS: I'll try later today installing 3.1 and updating it on my thinkpad running XP SP1 and some customized corporate fixes to see if the same problem occur. (hopefully not since RSA is working fine and is based on eclipse 3 iirc)
Forgot to add the JRE version: SUN 1.5.0_03, build 1.5.0_03-b07.
I too am having the same problem. With I am running W2K SP4. I have the problem with 3.1 and 3.0.2 when I tried to back up to that. I have tried with JVM 1.5_04 and 1.4.2_08 and the prblem does not change. It happens %100 of the time under 3.1 any EMF piece. (I have tried MANY combinations of selections.) And it has happened with MANY of the plug-ins I have tried. Size does not seem to matter.
Hello, I also experinced the problem. If I use the Help->Software Updates->Find and Install... and try to install any new plugin/update the download starts but then after a short time the network connection freezes. A ping with option -t which I run parallel also stops with 'exceeded timelimit'. If I deactivate the network connection and activate it again the installation continues but after next few seconds the problem occurs again. So I can try to finish the installation by deactivating/activating the network connection again and again. But sometimes then an error message in a new window appears: Problem Occured Update operation has failed and I am only able to click OK and then the complete installation failed. After closing Eclipse, the network connection comes back. The problem occurs always using the update manager and not occasionally. I have two network adaptors in my PC, on is an ADSL connection from German T- Online the other one is a LAN connection to a proxy server which is connected to the internet by a 1 MBit SDSL line. On both the described problem occurs. I use WindowsXP Professional and Eclipse Version: 3.1.0, Build id: I20050627-1435
I too have experienced this bug, but interestingly only on my home PC and not my laptop. I saw above that Jonas specified the Marvell Yukon network card, which is also what I'm using in the machine that doesn't work. Does anyone (or everyone) else who is experiencing this bug use the same network adapter?
Like Brian and Jonas, I too have the Marvell Yukon adapter. I tried the updater again with another nic and everything went fine. That must be the problem then (if all the other reportees also have the same network adapter). It still very strange that it only occurs with Eclipse.
I am running on an HP N800V laptop with a Intel Pro 100 VE ethernet controller and still experience the problem.
I have tried reproducing and have had no luck. Netstat showed no suspicious connections. I was trying from work in Toronto. I have Marvell Yukon at home and have seen no problems downloading updates from eclipse.org. Do you download from Eclipse.org or other sites when the problem appears? Re comment #6: The site http://jboss.sourceforge.net/jbosside/updates is occasionally very slow depending on the request. I was able to download large jars in couple of seconds and some small jar took very long. Steady download, of 300 bytes per second, never timing out. Not a problem with Install/Update as I have seen the same downloading these jars using Internet Explorer.
Konrad: Did you try to install the CDT (http://download.eclipse.org/tools/cdt/releases/new) with the Yukon nic? I can reproduce it pretty reliably (I only succeeded once in about 20 attempts).
I tried different features yesterday, and tried CDT today using Marvell Yukon. Everything installed smoothly. I have noticed larger then expected number of connections reported by netstat, sometimes with 7 established connection (just one Eclipse instance running): www.eclipse.org:http CLOSE_WAIT www.eclipse.org:http ESTABLISHED www.eclipse.org:http CLOSE_WAIT www.eclipse.org:http CLOSE_WAIT www.eclipse.org:http ESTABLISHED www.eclipse.org:http TIME_WAIT www.eclipse.org:http CLOSE_WAIT www.eclipse.org:http ESTABLISHED www.eclipse.org:http ESTABLISHED www.eclipse.org:http ESTABLISHED www.eclipse.org:http ESTABLISHED www.eclipse.org:http ESTABLISHED It is not good, but should be the cause of this bug.
Konrad, is the capability to download several plug-ins in parallel enabled in the current code? I remember Dorian experimenting with it but don't know if it is still there. If so, that may explain multiple connections. It may be that if we try to download multiple plug-ins and the connection is slow/non- responsive, we may quickly reach our own internal limit of 10 connection threads.
There were no performance gains, and according to Dorian, parallel download is not enabled. The multiple connections that are present should be eliminated in the long run, or sooner if they are the cause, but this bug talks about large updates and we should try to reproduce and unplug it so updates flow well. It would be worth fixing for 3.1.1 if we can reproduce and fix.
Sorry for not getting back regarding 3.1 on other hardware arhitecture, but I see others have already reported that a common element seems to be the Yukon adapter. Art however reported that he had the problem with a Intel Pro 100 VE as well, so it's not entirely clear if it's driver/hardware/JRE or Eclipse JNI related.. Eclipse 3.1 worked fine on my Thinkpad T41 btw (no surprise really) Konrad since the Yukon seems suspicious, I'll give you some more details relating to my network adapter hoping that you'll be able to reproduce the bug. [from msinfo32] Driver: c:\windows\system32\drivers\yk51x86.sys (7.29.4.3 built by: WinDDK, 218,75 KB (224 000 bytes), 2004-10-25 01:47) [From Yukon Diagnostics] PN: 88E8001 PCI_IDS DEVICE_ID: 4320 VENDOR_ID: 11AB SUBSYSTEM_ID: 811A SUBVENDOR_ID: 1043 PCI_DATA IOBASE: 9000 MEMBASE: ED000000 IRQ: 17 BUS_CLOCK: 33 SLOT: 9 SLOTSIZE: 32 CACHE_LINE_SIZE: 8 LATENCY: 32 MISCELLANEOUS PMD Type: 10/100/1000BT Connector: UTP Port(s): 1 RAM: 64kB HW Revision: 1.3 FPROM: Inactive
I'm having the same problem, using a Marvel Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller.
In a sort moment of realization, I remembered that I have two built in network adapters on the same MoBo (an Asus A7N8X) and I swapped the TP-cable to the socket for the other adapter, and voala all Eclipse updates downloaded and installed without a hitch! The network adapter which worked was a NVIDIA nForce MCP Networking Controller w. driver nvenet.sys (4.14.01.0346, 69,00 KB (70 656 bytes), 2004-10-25 01:48). I'm now leaning pretty firmly towards the problem being the Yukon card or it's driver. As pointed out earlier by Vincent, I also think it's strange though that I've only encountered this problem with Eclipse update and no other software!? So, a workaround for Yukon owners for now seems to be: "Swap NIC" since Eclipse won't currently play ball with that specific product.
(In reply to comment #22) > I've only encountered this problem with Eclipse update and no other software!? > So, a workaround for Yukon owners for now seems to be: "Swap NIC" since Eclipse > won't currently play ball with that specific product. It is great news that it worked for you. Regarding Eclipse comment, I would not so much look at Eclipse itself, rather the particular JDK you are using because Update is using only java.net APIs for networking calls. It is possible that the particular JDK implementation has issues with the particular driver. Perhaps you can experiment with updating the JDK and/or updating the network card driver.
My sofware is the same: c:\windows\system32\drivers\yk51x86.sys (7.29.4.3 built by: WinDDK, but it is not exactly the same hardware. I should have posted it earlier. I have: Marvell Yukon 88E8053 PCI-E Gigabit Ethernet, that came built-in on the Asus P5AD2 Deluxe. Marwell seems to have a newer driver then available with OS updates, you can try to see if it makes any difference. Otherwise, I hope you guys still have some warranty left on the hardware :-) The bug is still open for investigation, since Art reported problem with Intel Pro 100 VE, and with Yukon chip, Eclipse should not be the only software incompatible with it.
(In reply to comment #23) Dejan, regarding the eclipse comment it might very well have been unjust (didn't intend to assign any blame). Simply meant that as it currently stands the eclipse update is a piece of software which very clearly reveals *some kind* of network related anomaly for owners certain Yukon cards. It might very well be the java implementation, the NIC driver, the hardware or something else. I also wasn't certain whether any JNI was used or not for that specific eclipse code (I've seen c++ files in eclipse before, so I couldn't roll out eclipse fully without having looked through the code). As for your suggestion of testing different JVM/NIC driver combos .. The latter I won't test but the former I will. Tried to update the Yukon driver twice before and each time the NIC stopped working (had to resolve to system-restore to get network connection going again :-( ). Perhaps if someone else has managed to successfully upgrade the driver for their 88E8001 in the past, they might be able to do that kind of testing. As for testing with various VMs. I've now also tried Sun JDK 1.4.2_02 and IBM Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20040926 (JIT enabled: jitc)). Both exhibiting the same symptom (NIC freeze). Can you perhaps give some hints regarding what plugin and class I could set a breakpoint in, before the network code is invoked (and the problem manifests itself)? I checked out all *update* plugins but it's like finding a needle in a stack (as with all well abstracted systems, gaining flexibility by paying in complexity).
My comment was simply reflecting the fact that we use java.net classes for networking needs and these are 100% pure Java classes (i.e. we don't have native code for updates and installs). I will let Konrad or Branko point you at the place in code to play with (they should not better :-).
And of course, it should be 'know better' not 'not better'.
I found the culprit on my machine, unclear why it would interfere but the Microsoft Virtual PC driver that was bound to the adapter seemed to cause the lockup. I disabled it (Virtual Machine Network Services), and the eclipse updater worked without a problem. The problem effected both my intel pro 10/100 ethernet and my compaq 802.11b adapter... Does anyone else have Virtual PC 2004 installed and experience this problem? Does anyone have access to install VPC 2004 to test the conflict?
(In reply to comment #28) > Does anyone else have Virtual PC 2004 installed and experience this problem? Interesting. I *had* a version of Virtual PC installed (an older version since before VPC was bought by Microsoft). Perhaps there is still some hidden binding (due to a crappy uninstaller?) leeching on my network adapter (without me seeing it in either the services window or in the adapter bindings tab). I do however have VMware installed. However after stopping the VMware services and unbinding it from the adapter I still have the "freeze" problem. The search goes on I fear ...
I tried with Vritual PC 2004, downloading Eclipse updates on host PC and virtual PC concurently, and other sotware on host that generates additional network traffic. I noticed no interference between them and no network freezing.
I was having the same problem. I thought it might have been my router (thing's a buggy POS). I actually implemented a new router using gentoo on a doorstop PC. That solved some other, unrelated issues I've been having, but not this one. I read the comments here (thanks for all the useful information, guys) and realized that I too have the Yukon NIC (it is on the mobo). Here are the things I have tried in order: 1. Created a clean eclipse installation. I even deleted my ".metadata" folder in my workspace directory. 2. I upgraded the Yukon driver to the latest version (8.35.2.3 dated 7/20/2005). I tried it again without rebooting (it did not ask me to reboot after the install). This time the entire machine froze up! I had to reset it to get going again. 3. I have since tried it again after the reset with the same behavior as described in all the other posts. Eclipse did seem to timeout quicker, though, and when it did I was able to use the network again. I am back to square one on this. Please post if you solve this problem! Donley
I've seen this behavior and have debugged it up to the point the code enters the JDK classes. I cannot debug these, since I do not have a debug version of the sun java packages (aka rt.jar). In my experience, the sun.net package has proven to be temperamental and unreliable, and it seems to be causing the problem here. In particular the HttpClient and HttpURLConnection classes have caused problems for us in the past. By the way, I have tried this with both JDK 1.5 and 1.4.2_06. The stack when the error occurs indicates that HttpURLConnection.getLastModified() is doing a 'GET' and not as I would expect a 'HEAD' request. This may be causing Eclipse to hang, even though the web server (in my case Apache) successfully returns the request. Has anyone else traced it to the same point? Here's the captured stack: SocketInputStream.socketRead0(FileDescriptor, byte[], int, int, int) line: not available [native method] SocketInputStream.read(byte[], int, int) line: not available BufferedInputStream.fill() line: not available BufferedInputStream.read1(byte[], int, int) line: not available BufferedInputStream.read(byte[], int, int) line: not available HttpClient.parseHTTPHeader(MessageHeader, ProgressEntry) line: not available HttpClient.parseHTTP(MessageHeader, ProgressEntry) line: not available HttpURLConnection.getInputStream() line: not available HttpURLConnection.getHeaderField(String) line: not available HttpURLConnection(HttpURLConnection).getHeaderFieldDate(String, long) line: not available HttpURLConnection(URLConnection).getLastModified() line: not available HttpResponse.getLastModified() line: 215 UpdateManagerUtils.isSameTimestamp(URL, long) line: 807 FeaturePackagedContentProvider(FeatureContentProvider).asLocalReference(ContentReference, InstallMonitor) line: 192 FeaturePackagedContentProvider.getPluginEntryArchiveReferences(IPluginEntry, InstallMonitor) line: 165 Feature.install(IFeature, IFeatureReference[], IVerificationListener, IProgressMonitor) line: 420 SiteFile.install(IFeature, IFeatureReference[], IVerificationListener, IProgressMonitor) line: 74 ConfiguredSite.install(IFeature, IFeatureReference[], IVerificationListener, IProgressMonitor) line: 122 ConfiguredSite.install(IFeature, IVerificationListener, IProgressMonitor) line: 86 InstallOperation.execute(IProgressMonitor, IOperationListener) line: 72 BatchInstallOperation.execute(IProgressMonitor, IOperationListener) line: 84 InstallWizard2.install(IProgressMonitor) line: 373 InstallWizard2.access$1(InstallWizard2, IProgressMonitor) line: 370 InstallWizard2$2.run(IProgressMonitor) line: 465 ModalContext$ModalContextThread.run() line: 113
I have a workaround for this, it appears to me to be a bug in the Marvell Yukon drivers, and/or the way java accesses tcpip. Short: increase the number of Recieve & Transmit in the adapter properties, I increased to 200. Long: get to your adapter properties (device manager->network adaptors->marvell..->right click->properties). goto advanced & increase Number of Recieve & Number of Transmit Buffers, I increased from 50 to 200, perhaps overkill. I havent tried increasing only one setting (i'm running out of things to install :). this may help pinpoint where is causing problems.
I was having the same problem for the las few months. Every update that i tried failed during the verification process. But I don't have a YUKON NIC. I have got a ASUS P4C800 mobo with a 3Com Gigabit LOM (3C940)network controller onboard. Now i tried the workaraound ( see comment #33). It worked perfectly for not to big packages. If I select to much at once then the problem still comes up during the verification process.
I have the deadly combo Marvell Yukon/update freeze too. Until a solution will be found, here is how it worked (for me). Freeze: F1. Start update for CDT; update finds both CDT environment and CDT SDK. F2. Select BOTH to update. F3. Marvell Yukon have transmit and receive buffers set to 50. F4. Download succeeds until some 90%. Result: network freezes, DHCP address lost etc. Workaround: W0. update Marvell Yukon card buffers to 192 Also 128 seems working, or maybe it does not matter - read W2. W1. same as F1 W2. Select ONLY CDT to update, not also CDT SDK. W3. Update checks for download (already done in F2), install succeeds. W4. Repeat update for CDT SDK. Download + install succeeds. Result: No network freeze. Environment: OS : Windows XP SP2 Pro full updated; VMware NOT running (but not disabled) Network : Windows 2003 domain, DHCP-assigned 192.168.x.x Firewall: Windows firewall on workstation, ISA 2004 on server Net Card: Marvell Yukon 88E8001/8003/8010 PCI; driver version 8.32.2.3 Java : Java(TM) 2 Runtime Environment, Standard Edition; 1.5.0-b64 Eclipse : 3.1.1 Build id: M20050929-0840 CDT : 3.0.0
In case it helps someone else: I experienced this problem with my Intel Pro/100 VE (on an IBM ThinkPad T40). I installed the latest drivers from IBM and it seems to be fixed. At least, I was able to successfully install UML2 & JBossIDE (in the same shot, even), whereas before, I couldn't even get JBossIDE to install.
Just to confirm. Nick's workaround mentioned in comment 33 worked for me as well. Thanks Nick!
I'm experiencing the same problem, but with another network adapter: "Allied Telesyn AT2700FX PCI 100Mb" - fibre ethernet adapter. What I did as a workaround was to use the other network adapter of my computer (Intel PRO/1000 CT). Using this adapter everything works as expected.
*** Bug 143564 has been marked as a duplicate of this bug. ***
*** Bug 74382 has been marked as a duplicate of this bug. ***
(This worked for me. XP Pro SP2. 3COM 3C940 Gigabit Ethernet controller.
(In reply to comment #41) > (This worked for me. XP Pro SP2. 3COM 3C940 Gigabit Ethernet controller. Comment 33 worked for me. XP Pro SP2. 3COM 3C940 Gigabit Ethernet controller
I too have a 3COM 3C940 Gigabit adapter (integrated on the mainboard) and I suffer the same problems (so it's definitely just yukon). This happens quite often for me (not only with Eclipse, sometimes Azureus too, or even MS Outlook!). Smaller things like Subclipse work for me, larger stuff like CDT doesn't (if you're running out of things to test, simply uninstall CDT and install it again). The problem appears both on 3.1.x (I haven't been able to update to 3.1.2 because of it), as well as on 3.2RC6 (JRE 1.5.0_06 on WinXP SP2 but I don't think that matters) Comment 33 seems to do the trick for me as well. I think I remember that I was able to upgrade from 3.0 to 3.1 without problems, as well as install phpeclipse in 3.0, so there probably has to be a way to "fix" this in Eclipse, even though it's not really Eclipse's fault.
*** Bug 103776 has been marked as a duplicate of this bug. ***
*** Bug 108436 has been marked as a duplicate of this bug. ***
i encountered this problem on a Dell Latitude X300 while trying to update the Web Tools Platform. precisely the same symptoms, with the net dying for a while (noticed this while trying to browse the web waiting for WTP installation to finish) i cannot seem to control the X300's network devices as indicated in comment 33. the workarounds in comment 35 seem to do the trick for me, i.e. updating one component at a time and watching netstat output.
With WTP 1.5 RC5 (Eclipse 3.2RC7) I dont have problems with update manager. Now I can install SpringIDE with Update Site without any problem.
Can more people confirm this with rc7, maybe we can close this bug?
*** Bug 107475 has been marked as a duplicate of this bug. ***
*** Bug 122256 has been marked as a duplicate of this bug. ***
*** Bug 123056 has been marked as a duplicate of this bug. ***
Still experiencing this bug on Version: 3.2.0 - Build id: I20060602-1317 with large updates. Can't use the workaround posted in comment #33 as those options aren't available for my network driver (Netgear WG311v3). Running Windows XP SP2.
I dont have this bug anymore, I can install SpringIDE without problems. Im using e WTP 1.5 (Eclipse 3.2), WinXP.
Phil (comment #52), could you please try with 3.2.
I'm using version 3.2, see OP.
I'm experiencing the exact same problem on Eclipse 3.2 when trying to update to 3.2.1, using JDK 5 update 8, Windows XP SP2, on an ASUS P4C800 with the embedded 3Com Gigabit LOM (3C940). About a year ago I encountered the same problems, mainly when trying to do the large MyEclipse updates. I discovered setting the receive and transmit buffers to a higher value myself, and didn't had any problem anymore until today when trying to do the Eclipse 3.2.1 upgrade. The symptoms are exactly the same as everyone. During upgrading, the windows network stack is completely killed, nothing works anymore (no ping, no access to the local netwerk and certainly no internet). As soon as I quit Eclipse (or even just quit the updater), all networking works again. Here are my current NIC settings: 802_1p support - disabled flowcontrol - asymmetrical and symmatrical hardware checksumming - on Interrup moderation - off log status messages - status messages Max IRQ per sec - 1500 Maximum Frame Size - 1514 Media Type - 10MB, Full Duplex Network Address - not present Number of receive buffers - 500 (which is the max) Number of transmit buffers - 200 (which is the max) Wake Up Capabilities - Both I have auto update enabled in Eclipse (download new update automatically and notify me when ready to install them). After starting Eclipse, downloading begins. In the progres view I see the different jars being downloaded e.g. Downloading: plugins/org.eclipse.ui.into.universal_3.2.1... etc ( xxk of xxxk bytes) After quite a long time, a dialog pops up: New updates are available and downloaded. Do you want to review and install them now? In my case two updates are listed: subversive the eclipse project updates (-> Eclipse 3.2.1 -> Eclipse Project SDK 3.2.1.r321...) I keep both selected and continue. The update manager dialog then comes up with the text: "Download and install selected features". In the Windows task manager, I see that network activity starts again. This activity lasts for about 20 seconds, after which all networking in Windows is completely killed. After a few more seconds, another dialog pops up saying: An exception occured while downloading feature from http://update.eclipse.org/updates/3.2/features/org.eclipse.rcp_3.2.1.r321_v20060801-wekW2BxmcpPUOoq.jar If I cancel this dialog (and the entire update process with it), networking is restored. I tried the solution propossed in comment 35 to only update one item at a time (I tried to only update Eclipse, skipping subversive), but exactly the same things happened. Last year increasing the buffers helped, but I can't increase them anymore as they are already maxed out. With the current settings I have no problems whatshowever with downloading in either getright, firefox, emule, bittorent (even all of those together) etc. Only Eclipse is causing these problems. On a side note: Why is the installer trying to download more stuff when the dialog suggest everything has already been downloaded ("New updates are available and downloaded")? Why does the installer download everything again after I restart Eclipse? Trying to experiment with the different settings of my NIC is *extremely* time consuming this way.
As an update to comment 56: I managed to get the update installed by disabling auto update, doing a manual online install (help -> software updates -> find and install) and choosing an FTP source to download from in the mirror selection dialog. I don't know whether its the fact that I did a manual install or the fact that I choose an FTP source solved this. But as comment 32 suggest, the problem may be in the HttpClient and HttpURLConnection classes which of course aren't used for FTP connections.
See 107475 The problem is Win XP has a limited # of concurrent connections built into it. And the update manager makes liberal use of connections...
Created attachment 79101 [details] Flash-movie (Camtasia Studio) showing the behaviour. This movie shows the behaviour. I have deleted about 6 minutes of frames where nothing's actually happening (just 'waiting'), but eventually you can see the network-stack freeze up. I'm running Windows XP Pro, SP2, all up-to-date. No firewall/virusscanner (on this machine that is) Eclipse 'Europa' 3.3.0 A previous installation of Eclipse (3.2 I believe, but not certain) got all screwed up after these auto-updates failed.
The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2.
