First attempt to use Eclipse Callisto update site not very inspiring

Posted on July 3rd, 2006 in General, Software, Tech.

I’ve used update sites for various Eclipse plugins over the years, but for the most part have manually downloaded and linked to WTP. Now that Callisto is ready, I decided to go the update manager route. After installing a bare Eclipse SDK, I selected the Callisto site, picked the WTP components, BIRT, and all their dependencies, and let it go ahead and download.

After 10 minutes, I found the update manager stuck with a message that it was unpacking a certain .gz file that is part of the download. The dialog was still quite live, so after seeing that nothing was changing (71% completion percentage) I hit cancel. Now the cancel button is greyed out, but nothing else has changed. It looks like I’m going toi have to simply kill the Eclipse process.

Not a great start for Callisto on my system…

Update 2006-7-4: On a 2nd attempt, same story, different archive. org.apache.cactus_1.7.2.v200606181221.jar.pack.gz is stuck. The status bar says 69% forever.

 

7 responses

  1. Rainer says:

    Added on July 4th, 2006 at 12:02 pm

    Colin,

    it might be a problem with your network card.
    Have a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=101575, a solution is provided in comment #33.

    Hope this helps,
    Rainer

  2. Colin Sampaleanu (blog author) says:

    Added on July 4th, 2006 at 12:08 pm

    Thanks, but the problem I have is at the unpacking stage, note the downloading stage.

    What I’ve noticed is that if I kill Eclipse (the launcher as well as the javaw process), there is still some sort of unpack utility in memory, coming from the JRE. It is the latter that is hanging I believe.

    What is quite strange is that as I said, I’ve used the updae manager for lots of things, some of them pretty large, like the AscpectJ AJDT, with no problems.

  3. Rainer says:

    Added on July 5th, 2006 at 1:41 am

    In my case the download went well, but when the feature was installed or verified eclipse freezed.
    It’s easy to recognize wether it’s the problem above, though: all network connection on your computer will hang. So if you can still surf the web or send a ping it’s a different problem.

    Rainer

  4. Ben Pryor says:

    Added on July 6th, 2006 at 11:22 am

    This sounds like the culprit might be the new Pack200 support in Callisto. Do you see a “unpack200″ process that appears to hang?

    I can suggest two things:

    1) Unpacking Pack200 files is very resource-intensive. If the unpack process is using lots of CPU give it some time. If it’s not CPU bound it may be genuinely hanging on you.

    2) Try running Eclipse under Java 1.4 - I believe this will disable the Pack200 support in the update manager.

  5. Olivier Brand says:

    Added on July 11th, 2006 at 2:11 pm

    All,

    I have the same problem on one of my laptop. The workaround is to go in the jdk and jre folders of your 1.5 install and rename the unpack200.exe files.
    Eclipse will not see these files and will proceeed with a standard/pre 1.5 install. This is a hack but better than rolling back to 1.4

    Hope this helps

  6. Fahim Farook says:

    Added on December 25th, 2006 at 7:50 pm

    I ran into the same problem yesterday but didn’t realize what the issue was till I got a lot of non-responding unpack200.exe processes at night when I shutdown the machine :) What I did today was launch the update, wait for it to freeze and then open TaskManager and see if the unpack200.exe process was actually doing anything. If not, then I killed the process and the update (appears to) progress fine from that point on. Not sure if this helps or not but thought I’d let you know :)

  7. Denis Jouvin says:

    Added on May 28th, 2007 at 7:22 am

    I had exactly the same problem.

    renaming the unpack200.exe works.

3 trackbacks

Leave a Reply