java.util.zip.ZipException: No such file or directory
 

Greetings.

I had been happily using LimeWire 2.3 on my Linux system for some time without problems. (So yes, I have the correct JRE installed, etc.) Today I downloaded and installed version 2.4. Here's what I get when I try to execute the program:

Obviously this error message would be much more useful if it told me exactly which file or directory LimeWire couldn't find. All my file permissions are set the same as they were for the previous version. Anyone encounter this problem before?

Re: java.util.zip.ZipException: No such file or directory
 

I was able to replicate your error above. You are getting that error because you are not executing the file from within the correct directory of the executing jar file (LimeWire.jar) or the file that you are using to execute the file in the directory isn't pointing to the right place (symlink named "runLimeWire").

example:

"ls" produces this ouput:

.
..
LimeWire/
LimeWireSrc/

"ls LimeWire" produces this output:

.
..
LimeWire
LimeWire.jar
LimeWire.lax

"java -jar LimeWire.jar" produces this output:

Exception in thread "main" java.util.zip.ZipException: No such file or directory
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at java.util.jar.JarFile.<init>(JarFile.java:55)


Similiar output as your own (debatebly almost exact). Now when I move to the correct directory, "cd LimeWire", and then run the command again, "java -jar LimeWire.jar", the program runs correctly.

altoine

Re: Re: java.util.zip.ZipException: No such file or directory
 

Nope. I've got a shell script which changes to the correct directory and executes the runlime.sh script provided with the installation. Even running runlime.sh manually from the command line produces the same error.

Interestingly, I can run LimeWire by just typing "java -jar RunLime.jar", but then I get a whole slough of errors (mostly FileNotFoundException) printed to the console:

Given that the LimeWireLinux.tgz available for download does not have any of the files mentioned above, my working theory is that someone forgot to recurse directories when making the tarball...

Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

Oops... that should read "java -jar LimeWire.jar", of course.

Re: Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

That too if the person isn't using the jar file that they are referencing in their message above. But you are right as it is LimeWire.jar now that I slowed down to think about it. thanks :)

altoine

Re: Re: Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

A quote on top of a quote. Let us go through the questioning process first before we next go for any further suggestions.

1.) What shell environment are you using (bash, czsh, ksh)?

2.) What is the script that you actually use? Can you please cut & paste it here?

3.) What is the output of your path? Type this command and pleae post it here:

echo $PATH

4.) What LimeWire package are you using (tgz or bin)?

5.) What glibc and GNU compiler are you using? Try this command to see:

rpm -qa | grep glibc & rpm -qa | grep libgc

6.) What is in your "/usr/bin" directory? Try this command to find out:

ls /usr/bin/j*

7.) What output do you get when you use this command? (Pleae post it here):

echo $JAVA_HOME

8.) If you want to try one of my solutions before I try the above, try this link:

http://www.gnutellaforums.com/showth...threadid=11187

HTH
altoine

Re: Re: Re: Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

Greetings.

I'm the OP. Here are the answers to your troubleshooting questions... you can assume you're talking to someone with a reasonable amount of Unix experience.

czsh? That's a new one for me... I'm using tcsh.

Nothing special:

#!/bin/tcsh
cd /usr/local/LimeWire
sh runlime.sh >& /dev/null &

This script is called /usr/bin/limewire.

/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/games

The tarball -- I already mentioned this.

glibc-devel-2.2.4-6mdk
glibc-2.2.4-9.1mdk

I have /usr/bin/java, which is a symlink to the jre1.3.1 Java wrapper script.

I don't have this environment variable defined.

Keep in mind that everything was working perfectly for me for LimeWire 2.3. In fact, I can still run 2.3 (which I have in a backup directory) without any problems. It's just 2.4 that won't run. Again, all file and directory names and permissions are unchanged from the previous installation.

Many thanks for any insights you may be able to offer.

Re: Re: Re: Re: Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

Excuse me for my delay in replying as I was away for a few days. I understand what you mean about your program script being able to work with the previous LimeWire version 2.3 as I have the same situation. I didn't have problems until I tried the 2.4 version. The link that I had given you earlier is what works 100% in a bash shell. I noticed from your prior post that when you printed your output, it has a non-bash default character "%" instead of "$". That gave me an early indication that my suggestive link will not work for you. Two, yes, you will have to set the environment variables for java to work by command line. That explained the lengthy error messages. I am greatful that I am speaking to someone with considerable *nix experience at it makes my assitance all the more easier to give.

Bad practice on my part but I incorporated them into the quote.

HTH

altoine

Re: Re: Re: Re: Re: Re: Re: Re: java.util.zip.ZipException: No such file or directory
 

Greetings, OP again.

I did exactly what you suggested: added an environment variable JAVA_HOME for my jre directory (I don't have the sdk) and made sure it was in my path. LimeWire still doesn't work.

I don't see why the change you suggested would have worked anyway, since I can still run LimeWire 2.4 manually with the java command; it just produces a million error messages about missing files and fonts (which were presumably supposed to be bundled in the tarball). If LimeWire really couldn't find Java or the standard libraries, it probably wouldn't have started up at all.

Have you or anyone else actually gotten the 2.4 tarball to work?

java.util.zip.ZipException: No such file or directory
 

I asked myself the same questions. That is why I downloaded the cvs to investigate it for myself. I will run a "diff" between cvs and version 2.3. Surprisingly, the suggestions that I gave, short of the experimental tcsh suggestions worked for me and others with their default user accounts using bash. Isn't there a way for you to try bash and then implement my suggestions from my link? I have just finished reconfiguring all of my distributions on my computers with the exception that I have gentoo and Linux From Scratch left to change. I had them all pretty much optimized as multimedia systems but because of my intensive involvement with developmental software, I had to make some drastic changes from repartitioning my drives to reconfiguring scripts. Under bash, all my distros rock. Red Hat 7.3, Mandrake 8.2, Mandrake Cooker, Linux From Scratch, and gentoo. I will have answers for you within a day (I hope) of why my suggestions work at all, let alone why they are necessary. One thing I do know for certain, they work 100% under bash as I have not been told different.

digging deep,
altoine

Additional Note
 

I yet don't know the difference RunLime.jar and LimeWire.jar but they both run the same and well without errors on my system. I can only run the commandline runLime.sh and not LimeWire the executeable. I have a hunch. Can you post all your compilers (rpm -qa|grep gc)? I think a library called libgcj and gcc-java maybe the true culprits. I had a brain fart in the previous post but now I am remember while java path was added into the .bashrc or .bash_profiles. It is added to allow you to have your downloaded java package to be chosen over any other first. Kaffe has residence in /usr/bin. When I had given you the suggestion for your tcsh shell environment, I should have explicitly stated that JAVA_HOME had to be first in your set path. Or simply instead of using the variable JAVA_PATH, just simply place the full path to your java executables like so:

set path = ( . /usr/java/j2jre1.4.0/bin, /usr/bin, /usr/sbin )

That way, no matter how many java jre and sdk packages you have installed the one you want used with LimeWire 2.4 will be chosen by default.

Re: Additional Note
 

perl-Msgcat-1.03-7mdk
libsigc++1.0-1.0.3-2mdk
gcc-cpp-2.96-0.62mdk
gcc-2.96-0.62mdk
gcc3.0-cpp-3.0.1-1mdk
gcc-c++-2.96-0.62mdk
gcombust-0.1.46-1mdk

Nope, no gccjava. Anyway, when you said to add JAVA_HOME to my path, I did add it to the beginning, not the end, and it still didn't work. <sigh>

If my perfectly normal out-of-the-box Mandrake installation (plus the Sun JRE) worked fine with LimeWire 2.3 and not LimeWire 2.4, then I think there is a bug in LimeWire 2.4. :(

Maybe I'll try the installer version... The only reason I didn't use it to begin with was spyware fears...

Re: Re: Additional Note
 

we can simply put /usr/java/j2re1.4.0/bin at the beginning. It really needs the path pointing to the bin of the java installation. Creating JAVA_HOME is created only to make it easier to change java versions on the fly at the commandline for purposes such as mine. You can simply set that into your path stateeent pointing to the "bin" and then log out and then back in. That is the best sure fire way to activate and use the changes as they are not always going to be used by simply opening up a new terminal or different terminal window when you are in a window manager. As it may not take effect simply because you may have already used an instance of that window prior to the changes. I had similiar effects until I did that. It is guaranteed to work.

altoine

This is weird. I download the tgz version of Lime since the bin version gave me java error when I try to run it. When i run the tgz version sh ./LimeWire.sh it gave me this post's java error but then I use java -jar LimeWire.jar then the whole program comes up and run. Oh well, I just have to remember to use this command line from now on.

Something Else to Try
 

Try to run runLime.sh instead of LimeWire.sh.

sh runLime.sh

HTH

altoine