Different LimeWire Problem

[matt95z]

Whenever I try to run LimeWire I get the error message
"Exception in thread "main" java.lang.NoClassDefFoundError: lax/nl/java/option/java/stack/"

I have j2re1.4.0_02 Installed I get the correct version numbers and everything when I type java -version.
It also says I have Java Hotspot Client VM.

I have tried everything I know how to do any help would be great

thanks

[askrieger]

Looks like the dreaded classpath strikes again! :(

The java vm is not finding one of the classes that it needs to run. Probably, but not necessarily, because it's looking in the wrong place. Usually this is because your classpath dosn't include the place where the needed file resides.

note added in proof: It may not be a classpath problem. It appears (to me) to be looking for java.stack when it should be looking for java.util.stack, but I can't believe that anyone would release software with an incorrect library function.

[rmarin2]

So what is the fix for this problem?

Thanks

[Hayl]

how are you running it?

from a command line or from a menu in the GUI?

[rmarin2]

Originally posted by Cybr099
how are you running it?

from a command line or from a menu in the GUI?

Well I'm forced to run it from command line 'sh runLime.sh' because of the ClassPath error when run with ./LimeWire.

[mdwatts]

See if the following helps that X_console posted earlier in another thread.

Adjust where necessary.


ln -s /usr/local/share/jdk-1.4 /urs/local/share/jdk

This symlinks the directory to /usr/local/share/jdk Now edit ~/.bash_profile and add the following:

code:
export PATH="$PATH:/usr/local/share/jdk/bin"


Now type source ~/.bash_profile
You should now be able to use javac and java.

[askrieger]

If my diagnosis of the problem was correct, (which it might not be), you have two choices. The easiest is to change your class path to include ".", which you should do anyway if your going to use java. See the NHF for detailed instructions. If you're still having problems, try to get a new version version of limewire.:)

[rmarin2]

Originally posted by mdwatts
See if the following helps that X_console posted earlier in another thread.

Adjust where necessary.



I've already made those additions to my .bashrc file and still nothing.. (I can run javac and java from anywhere) :(

-Rich

[rmarin2]

Originally posted by matt95z
"Exception in thread "main" java.lang.NoClassDefFoundError: lax/nl/java/option/java/stack/"


The problem is that ./LimeWire references LimeWire.lax, which is looking for a java program called Launch Anywhere at the path above. I'm still pretty much new to linux but there should be a work around for this.

I hate having to go into the console and run sh runLime.sh each time I want to use limewire. I have yet to figure out how to create a shortcut that will allow me us the sh command.

Thanks for all the info! Much obliged!! :)

[Xsecrets]

I think limewire broke something in their latest build. I have used limewire for a while now and I recently reinstalled and I am using the same java that I was before set up exactly the same, but the lime wire I downloaded gives the exact same errors you are talking about and I have to run the actual .jar file. When I do that it works just fine. something in their script doesn't work anymore. and I haven't had the time or inclination to tear it apart and find out what the problem is.

[askrieger]

Is LimeWire open source? Based on what I've seen in this thread it appears that somewhere in the lax program there is a line that says "java.stack" when it should say "java.util.stack". As I said before, it's hard to believe that anyone could release an update that doesn't work, but ...

If it's open source just grep the lax source for java.stack, change the line, and javac. If it's not open source, send the developer a nasty note.:)

[Xsecrets]

No it's not open source. And I think the only problem is in the script. when you install limewire it creates a dir in your home dir and it also puts a script in your home dir that starts the program. The script errors out but it you go into the dir and run the .jar file it works fine. I know the error seems odd for a script file, but It has to be in there somewhere. And even though it's not open source still should be easy enough to look through the script and find the error if one was so inclined. I'm lazy though and just run the .jar file instead.