Comments on: First attempt to use Eclipse Callisto update site not very inspiring

by: First attempt to use Eclipse Callisto update site not very inspiring

Mon, 26 Nov 2007 07:20:41 +0000

[…] First attempt to use Eclipse Callisto update site not very inspiring 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 […] Tue, 04 Jul 2006 01:57:55 +0000 General on sampa : colin’s blog http://blog.exis.com/colin/archives/2006/07/03/first-attempt-to-use-eclipse-callisto-update-site-not… - Original Article […]

by: Denis Jouvin

Mon, 28 May 2007 12:22:45 +0000

I had exactly the same problem.

renaming the unpack200.exe works.

by: server - somdaj.com » Problem using Eclipse’s Update Manager to install WST

Tue, 13 Feb 2007 23:01:24 +0000

[…] So, I go to install the SpringIDE plugin, using the Callisto installation directions. I get part of the way through it, and receive an error, informing me that an internal error regarding the update manager’s zip deflater has occurred, and it can’t go on. After a bit of googling… I find this entry on Colin’s blog, and follow Olivier’s advice. So, I do a ‘mv /usr/local/jdk1.5.0_11-64/bin/unpack22 /usr/local/jdk1.5.0_11-64/bin/unpack22.findme’ (Java HotSpt 64-Bit Server VM build 1.5.0_11-b03, mixed mode running on SLED 10 by the way), try the eclipse update manager process again, and voila, it works. […]

by: Problem using Eclipse’s Update Manager to install WST | OpenLogic Blogs

Tue, 13 Feb 2007 22:19:58 +0000

[…] So, I go to install the SpringIDE plugin, using the Callisto installation directions. I get part of the way through it, and receive an error, informing me that an internal error regarding the update manager's zip deflater has occurred, and it can't go on. After a bit of googling… I find this entry on Colin's blog, and follow Olivier's advice. So, I do a mv /usr/local/jdk1.5.0_11-64/bin/unpack22 /usr/local/jdk1.5.0_11-64/bin/unpack22.findme (Java HotSpt 64-Bit Server VM build 1.5.0_11-b03, mixed mode running on SLED 10 by the way), try the eclipse update manager process again, and voila, it works. […]

by: Fahim Farook

Tue, 26 Dec 2006 00:50:00 +0000

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

by: Olivier Brand

Tue, 11 Jul 2006 19:11:39 +0000

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

by: Ben Pryor

Thu, 06 Jul 2006 16:22:41 +0000

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.

by: Rainer

Wed, 05 Jul 2006 06:41:33 +0000

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

by: Colin Sampaleanu

Tue, 04 Jul 2006 17:08:47 +0000

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.

by: Rainer

Tue, 04 Jul 2006 17:02:41 +0000

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