Skip to main content

Exception: java.lang.NoClassDefFoundError

Recently, I encountered an unusual exception while executing a Java program on my Linux system :
I wrote a simple “Hello World” program and compiled it using javac compiler. When I tried executing this “Hello World” program I got this error:

Exception in thread “main” java.lang.NoClassDefFoundError

I diagnosed my system environment variables, checking if they are not set properly :

My Java is installed at :
/usr/local/j2sdk1.4.2_03/

$ echo $JAVA_HOME
/usr/local/j2sdk1.4.2_03

$ echo $CLASSPATH
/usr/local/j2sdk1.4.2_03/bin

$ echo $PATH
/usr/local/j2sdk1.4.2_03/bin

All variables are set correctly but still i was getting this “Exception in thread “main” java.lang.NoClassDefFoundError” error.

Then after lot of struggle I found the problem :

In Redhat systems even though we installed the RPM of Sun’s JRE there is still an OLD version of JAVA binary at /usr/bin.

Solution :

I moved this old version of java binary to :
mv /usr/bin/java /usr/bin/java.old

and created a link to latest version of java binary
ln -s /usr/java/jre1.4.2_03/bin/java /usr/bin/java

Basically, these steps replaced the old version of java with the version of java we are using and finally my “Hello World” program started working.
Labels:

Comments

Post a Comment

Popular posts from this blog

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA
Post a Comment
Read more

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…
Post a Comment
Read more