Ошибка java lang noclassdeffounderror

While it’s possible that this is due to a classpath mismatch between compile-time and run-time, it’s not necessarily true.

It is important to keep two or three different exceptions straight in our head in this case:

1. java.lang.ClassNotFoundException This exception indicates that the class was not found on the classpath. This indicates that we were trying to load the class definition, and the class did not exist on the classpath.

2. java.lang.NoClassDefFoundError This exception indicates that the JVM looked in its internal class definition data structure for the definition of a class and did not find it. This is different than saying that it could not be loaded from the classpath. Usually this indicates that we previously attempted to load a class from the classpath, but it failed for some reason — now we’re trying to use the class again (and thus need to load it, since it failed last time), but we’re not even going to try to load it, because we failed loading it earlier (and reasonably suspect that we would fail again). The earlier failure could be a ClassNotFoundException or an ExceptionInInitializerError (indicating a failure in the static initialization block) or any number of other problems. The point is, a NoClassDefFoundError is not necessarily a classpath problem.

answered Aug 29, 2008 at 15:01

Here is the code to illustrate java.lang.NoClassDefFoundError. Please see Jared’s answer for detailed explanation.

NoClassDefFoundErrorDemo.java

public class NoClassDefFoundErrorDemo {
    public static void main(String[] args) {
        try {
            // The following line would throw ExceptionInInitializerError
            SimpleCalculator calculator1 = new SimpleCalculator();
        } catch (Throwable t) {
            System.out.println(t);
        }
        // The following line would cause NoClassDefFoundError
        SimpleCalculator calculator2 = new SimpleCalculator();
    }

}

SimpleCalculator.java

public class SimpleCalculator {
    static int undefined = 1 / 0;
}

answered Feb 13, 2015 at 19:20

NoClassDefFoundError In Java

Definition:

1. Java Virtual Machine is not able to find a particular class at runtime which was available at compile time.

2. If a class was present during compile time but not available in java classpath during runtime.

Examples:

1. The class is not in Classpath, there is no sure shot way of knowing it but many times you can just have a look to print System.getproperty(«java.classpath») and it will print the classpath from there you can at least get an idea of your actual runtime classpath.

2. A simple example of NoClassDefFoundError is class belongs to a missing JAR file or JAR was not added into classpath or sometimes jar’s name has been changed by someone like in my case one of my colleagues has changed tibco.jar into tibco_v3.jar and the program is failing with java.lang.NoClassDefFoundError and I were wondering what’s wrong.

3. Just try to run with explicitly -classpath option with the classpath you think will work and if it’s working then it’s a sure short sign that someone is overriding java classpath.

4. Permission issue on JAR file can also cause NoClassDefFoundError in Java.
5. Typo on XML Configuration can also cause NoClassDefFoundError in Java.
6. when your compiled class which is defined in a package, doesn’t present in the same package while loading like in the case of JApplet it will throw NoClassDefFoundError in Java.

Possible Solutions:

1. The class is not available in Java Classpath.
2. If you are working in J2EE environment than the visibility of Class among multiple Classloader can also cause java.lang.NoClassDefFoundError, see examples and scenario section for detailed discussion.
3. Check for java.lang.ExceptionInInitializerError in your log file. NoClassDefFoundError due to the failure of static initialization is quite common.
4. Because NoClassDefFoundError is a subclass of java.lang.LinkageError it can also come if one of it dependency like native library may not available.
5. Any start-up script is overriding Classpath environment variable.
6. You might be running your program using jar command and class was not defined in manifest file’s ClassPath attribute.

Resources:

3 ways to solve NoClassDefFoundError

java.lang.NoClassDefFoundError Problem patterns

answered Aug 10, 2016 at 17:16

I have found that sometimes I get a NoClassDefFound error when code is compiled with an incompatible version of the class found at runtime. The specific instance I recall is with the apache axis library. There were actually 2 versions on my runtime classpath and it was picking up the out of date and incompatible version and not the correct one, causing a NoClassDefFound error. This was in a command line app where I was using a command similar to this.

set classpath=%classpath%;axis.jar

I was able to get it to pick up the proper version by using:

set classpath=axis.jar;%classpath%;

answered Aug 29, 2008 at 15:06

One interesting case in which you might see a lot of NoClassDefFoundErrors is when you:

1. throw a RuntimeException in the static block of your class Example
2. Intercept it (or if it just doesn’t matter like it is thrown in a test case)
3. Try to create an instance of this class Example

static class Example {
    static {
        thisThrowsRuntimeException();
    }
}

static class OuterClazz {

    OuterClazz() {
        try {
            new Example();
        } catch (Throwable ignored) { //simulating catching RuntimeException from static block
            // DO NOT DO THIS IN PRODUCTION CODE, THIS IS JUST AN EXAMPLE in StackOverflow
        }

        new Example(); //this throws NoClassDefFoundError
    }
}

NoClassDefError will be thrown accompanied with ExceptionInInitializerError from the static block RuntimeException.

This is especially important case when you see NoClassDefFoundErrors in your UNIT TESTS.

In a way you’re «sharing» the static block execution between tests, but the initial ExceptionInInitializerError will be just in one test case. The first one that uses the problematic Example class. Other test cases that use the Example class will just throw NoClassDefFoundErrors.

Ram PatraRam Patra

16k13 gold badges65 silver badges76 bronze badges

I was using Spring Framework with Maven and solved this error in my project.

There was a runtime error in the class. I was reading a property as integer, but when it read the value from the property file, its value was double.

Spring did not give me a full stack trace of on which line the runtime failed.
It simply said NoClassDefFoundError. But when I executed it as a native Java application (taking it out of MVC), it gave ExceptionInInitializerError which was the true cause and which is how I traced the error.

@xli’s answer gave me insight into what may be wrong in my code.

I get NoClassFoundError when classes loaded by the runtime class loader cannot access classes already loaded by the java rootloader. Because the different class loaders are in different security domains (according to java) the jvm won’t allow classes already loaded by the rootloader to be resolved in the runtime loader address space.

Run your program with ‘java -javaagent:tracer.jar [YOUR java ARGS]’

It produces output showing the loaded class, and the loader env that loaded the class. It’s very helpful tracing why a class cannot be resolved.

// ClassLoaderTracer.java
// From: https://blogs.oracle.com/sundararajan/entry/tracing_class_loading_1_5

import java.lang.instrument.*;
import java.security.*;

// manifest.mf
// Premain-Class: ClassLoadTracer

// jar -cvfm tracer.jar manifest.mf ClassLoaderTracer.class

// java -javaagent:tracer.jar  [...]

public class ClassLoadTracer 
{
    public static void premain(String agentArgs, Instrumentation inst) 
    {
        final java.io.PrintStream out = System.out;
        inst.addTransformer(new ClassFileTransformer() {
            public byte[] transform(ClassLoader loader, String className, Class classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer) throws IllegalClassFormatException {

                String pd = (null == protectionDomain) ? "null" : protectionDomain.getCodeSource().toString();
                out.println(className + " loaded by " + loader + " at " + new java.util.Date() + " in " + pd);

                // dump stack trace of the thread loading class 
                Thread.dumpStack();

                // we just want the original .class bytes to be loaded!
                // we are not instrumenting it...
                return null;
            }
        });
    }
}

answered Sep 9, 2015 at 12:02

yoAlex5yoAlex5

26.6k8 gold badges180 silver badges191 bronze badges

In case you have generated-code (EMF, etc.) there can be too many static initialisers which consume all stack space.

See Stack Overflow question How to increase the Java stack size?.

manuelvigarciamanuelvigarcia

1,3961 gold badge18 silver badges31 bronze badges

I fixed my problem by disabling the preDexLibraries for all modules:

dexOptions {
        preDexLibraries false
        ...

answered Feb 5, 2018 at 2:34

Ben WatersBen Waters

1471 silver badge8 bronze badges

logbasexlogbasex

1,3921 gold badge13 silver badges18 bronze badges

NoClassDefFoundError can also occur when a static initializer tries to load a resource bundle that is not available in runtime, for example a properties file that the affected class tries to load from the META-INF directory, but isn’t there. If you don’t catch NoClassDefFoundError, sometimes you won’t be able to see the full stack trace; to overcome this you can temporarily use a catch clause for Throwable:

try {
    // Statement(s) that cause(s) the affected class to be loaded
} catch (Throwable t) {
    Logger.getLogger("<logger-name>").info("Loading my class went wrong", t);
}

answered Sep 27, 2018 at 20:30

priyanka_raopriyanka_rao

4651 gold badge4 silver badges20 bronze badges

ST7ST7

2,1521 gold badge20 silver badges13 bronze badges

Brent BradburnBrent Bradburn

49.7k17 gold badges146 silver badges169 bronze badges

off99555off99555

3,5793 gold badges32 silver badges46 bronze badges

pixelpixel

8,90416 gold badges72 silver badges135 bronze badges

answered Jul 14, 2016 at 19:46

I got this message after removing two files from the SRC library, and when I brought them back I kept seeing this error message.

My solution was: Restart Eclipse. Since then I haven’t seen this message again

While it’s possible that this is due to a classpath mismatch between compile-time and run-time, it’s not necessarily true.

It is important to keep two or three different exceptions straight in our head in this case:

1. java.lang.ClassNotFoundException This exception indicates that the class was not found on the classpath. This indicates that we were trying to load the class definition, and the class did not exist on the classpath.

2. java.lang.NoClassDefFoundError This exception indicates that the JVM looked in its internal class definition data structure for the definition of a class and did not find it. This is different than saying that it could not be loaded from the classpath. Usually this indicates that we previously attempted to load a class from the classpath, but it failed for some reason — now we’re trying to use the class again (and thus need to load it, since it failed last time), but we’re not even going to try to load it, because we failed loading it earlier (and reasonably suspect that we would fail again). The earlier failure could be a ClassNotFoundException or an ExceptionInInitializerError (indicating a failure in the static initialization block) or any number of other problems. The point is, a NoClassDefFoundError is not necessarily a classpath problem.

answered Aug 29, 2008 at 15:01

Here is the code to illustrate java.lang.NoClassDefFoundError. Please see Jared’s answer for detailed explanation.

NoClassDefFoundErrorDemo.java

public class NoClassDefFoundErrorDemo {
    public static void main(String[] args) {
        try {
            // The following line would throw ExceptionInInitializerError
            SimpleCalculator calculator1 = new SimpleCalculator();
        } catch (Throwable t) {
            System.out.println(t);
        }
        // The following line would cause NoClassDefFoundError
        SimpleCalculator calculator2 = new SimpleCalculator();
    }

}

SimpleCalculator.java

public class SimpleCalculator {
    static int undefined = 1 / 0;
}

answered Feb 13, 2015 at 19:20

NoClassDefFoundError In Java

Definition:

1. Java Virtual Machine is not able to find a particular class at runtime which was available at compile time.

2. If a class was present during compile time but not available in java classpath during runtime.

Examples:

1. The class is not in Classpath, there is no sure shot way of knowing it but many times you can just have a look to print System.getproperty(«java.classpath») and it will print the classpath from there you can at least get an idea of your actual runtime classpath.

2. A simple example of NoClassDefFoundError is class belongs to a missing JAR file or JAR was not added into classpath or sometimes jar’s name has been changed by someone like in my case one of my colleagues has changed tibco.jar into tibco_v3.jar and the program is failing with java.lang.NoClassDefFoundError and I were wondering what’s wrong.

3. Just try to run with explicitly -classpath option with the classpath you think will work and if it’s working then it’s a sure short sign that someone is overriding java classpath.

4. Permission issue on JAR file can also cause NoClassDefFoundError in Java.
5. Typo on XML Configuration can also cause NoClassDefFoundError in Java.
6. when your compiled class which is defined in a package, doesn’t present in the same package while loading like in the case of JApplet it will throw NoClassDefFoundError in Java.

Possible Solutions:

1. The class is not available in Java Classpath.
2. If you are working in J2EE environment than the visibility of Class among multiple Classloader can also cause java.lang.NoClassDefFoundError, see examples and scenario section for detailed discussion.
3. Check for java.lang.ExceptionInInitializerError in your log file. NoClassDefFoundError due to the failure of static initialization is quite common.
4. Because NoClassDefFoundError is a subclass of java.lang.LinkageError it can also come if one of it dependency like native library may not available.
5. Any start-up script is overriding Classpath environment variable.
6. You might be running your program using jar command and class was not defined in manifest file’s ClassPath attribute.

Resources:

3 ways to solve NoClassDefFoundError

java.lang.NoClassDefFoundError Problem patterns

answered Aug 10, 2016 at 17:16

I have found that sometimes I get a NoClassDefFound error when code is compiled with an incompatible version of the class found at runtime. The specific instance I recall is with the apache axis library. There were actually 2 versions on my runtime classpath and it was picking up the out of date and incompatible version and not the correct one, causing a NoClassDefFound error. This was in a command line app where I was using a command similar to this.

set classpath=%classpath%;axis.jar

I was able to get it to pick up the proper version by using:

set classpath=axis.jar;%classpath%;

answered Aug 29, 2008 at 15:06

One interesting case in which you might see a lot of NoClassDefFoundErrors is when you:

1. throw a RuntimeException in the static block of your class Example
2. Intercept it (or if it just doesn’t matter like it is thrown in a test case)
3. Try to create an instance of this class Example

static class Example {
    static {
        thisThrowsRuntimeException();
    }
}

static class OuterClazz {

    OuterClazz() {
        try {
            new Example();
        } catch (Throwable ignored) { //simulating catching RuntimeException from static block
            // DO NOT DO THIS IN PRODUCTION CODE, THIS IS JUST AN EXAMPLE in StackOverflow
        }

        new Example(); //this throws NoClassDefFoundError
    }
}

NoClassDefError will be thrown accompanied with ExceptionInInitializerError from the static block RuntimeException.

This is especially important case when you see NoClassDefFoundErrors in your UNIT TESTS.

In a way you’re «sharing» the static block execution between tests, but the initial ExceptionInInitializerError will be just in one test case. The first one that uses the problematic Example class. Other test cases that use the Example class will just throw NoClassDefFoundErrors.

Ram PatraRam Patra

16k13 gold badges65 silver badges76 bronze badges

I was using Spring Framework with Maven and solved this error in my project.

There was a runtime error in the class. I was reading a property as integer, but when it read the value from the property file, its value was double.

Spring did not give me a full stack trace of on which line the runtime failed.
It simply said NoClassDefFoundError. But when I executed it as a native Java application (taking it out of MVC), it gave ExceptionInInitializerError which was the true cause and which is how I traced the error.

@xli’s answer gave me insight into what may be wrong in my code.

I get NoClassFoundError when classes loaded by the runtime class loader cannot access classes already loaded by the java rootloader. Because the different class loaders are in different security domains (according to java) the jvm won’t allow classes already loaded by the rootloader to be resolved in the runtime loader address space.

Run your program with ‘java -javaagent:tracer.jar [YOUR java ARGS]’

It produces output showing the loaded class, and the loader env that loaded the class. It’s very helpful tracing why a class cannot be resolved.

// ClassLoaderTracer.java
// From: https://blogs.oracle.com/sundararajan/entry/tracing_class_loading_1_5

import java.lang.instrument.*;
import java.security.*;

// manifest.mf
// Premain-Class: ClassLoadTracer

// jar -cvfm tracer.jar manifest.mf ClassLoaderTracer.class

// java -javaagent:tracer.jar  [...]

public class ClassLoadTracer 
{
    public static void premain(String agentArgs, Instrumentation inst) 
    {
        final java.io.PrintStream out = System.out;
        inst.addTransformer(new ClassFileTransformer() {
            public byte[] transform(ClassLoader loader, String className, Class classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer) throws IllegalClassFormatException {

                String pd = (null == protectionDomain) ? "null" : protectionDomain.getCodeSource().toString();
                out.println(className + " loaded by " + loader + " at " + new java.util.Date() + " in " + pd);

                // dump stack trace of the thread loading class 
                Thread.dumpStack();

                // we just want the original .class bytes to be loaded!
                // we are not instrumenting it...
                return null;
            }
        });
    }
}

answered Sep 9, 2015 at 12:02

yoAlex5yoAlex5

26.6k8 gold badges180 silver badges191 bronze badges

In case you have generated-code (EMF, etc.) there can be too many static initialisers which consume all stack space.

See Stack Overflow question How to increase the Java stack size?.

manuelvigarciamanuelvigarcia

1,3961 gold badge18 silver badges31 bronze badges

I fixed my problem by disabling the preDexLibraries for all modules:

dexOptions {
        preDexLibraries false
        ...

answered Feb 5, 2018 at 2:34

Ben WatersBen Waters

1471 silver badge8 bronze badges

logbasexlogbasex

1,3921 gold badge13 silver badges18 bronze badges

NoClassDefFoundError can also occur when a static initializer tries to load a resource bundle that is not available in runtime, for example a properties file that the affected class tries to load from the META-INF directory, but isn’t there. If you don’t catch NoClassDefFoundError, sometimes you won’t be able to see the full stack trace; to overcome this you can temporarily use a catch clause for Throwable:

try {
    // Statement(s) that cause(s) the affected class to be loaded
} catch (Throwable t) {
    Logger.getLogger("<logger-name>").info("Loading my class went wrong", t);
}

answered Sep 27, 2018 at 20:30

priyanka_raopriyanka_rao

4651 gold badge4 silver badges20 bronze badges

ST7ST7

2,1521 gold badge20 silver badges13 bronze badges

Brent BradburnBrent Bradburn

49.7k17 gold badges146 silver badges169 bronze badges

off99555off99555

3,5793 gold badges32 silver badges46 bronze badges

pixelpixel

8,90416 gold badges72 silver badges135 bronze badges

answered Jul 14, 2016 at 19:46

I got this message after removing two files from the SRC library, and when I brought them back I kept seeing this error message.

My solution was: Restart Eclipse. Since then I haven’t seen this message again

While it’s possible that this is due to a classpath mismatch between compile-time and run-time, it’s not necessarily true.

It is important to keep two or three different exceptions straight in our head in this case:

1. java.lang.ClassNotFoundException This exception indicates that the class was not found on the classpath. This indicates that we were trying to load the class definition, and the class did not exist on the classpath.

2. java.lang.NoClassDefFoundError This exception indicates that the JVM looked in its internal class definition data structure for the definition of a class and did not find it. This is different than saying that it could not be loaded from the classpath. Usually this indicates that we previously attempted to load a class from the classpath, but it failed for some reason — now we’re trying to use the class again (and thus need to load it, since it failed last time), but we’re not even going to try to load it, because we failed loading it earlier (and reasonably suspect that we would fail again). The earlier failure could be a ClassNotFoundException or an ExceptionInInitializerError (indicating a failure in the static initialization block) or any number of other problems. The point is, a NoClassDefFoundError is not necessarily a classpath problem.

answered Aug 29, 2008 at 15:01

Here is the code to illustrate java.lang.NoClassDefFoundError. Please see Jared’s answer for detailed explanation.

NoClassDefFoundErrorDemo.java

public class NoClassDefFoundErrorDemo {
    public static void main(String[] args) {
        try {
            // The following line would throw ExceptionInInitializerError
            SimpleCalculator calculator1 = new SimpleCalculator();
        } catch (Throwable t) {
            System.out.println(t);
        }
        // The following line would cause NoClassDefFoundError
        SimpleCalculator calculator2 = new SimpleCalculator();
    }

}

SimpleCalculator.java

public class SimpleCalculator {
    static int undefined = 1 / 0;
}

answered Feb 13, 2015 at 19:20

NoClassDefFoundError In Java

Definition:

1. Java Virtual Machine is not able to find a particular class at runtime which was available at compile time.

2. If a class was present during compile time but not available in java classpath during runtime.

Examples:

1. The class is not in Classpath, there is no sure shot way of knowing it but many times you can just have a look to print System.getproperty(«java.classpath») and it will print the classpath from there you can at least get an idea of your actual runtime classpath.

2. A simple example of NoClassDefFoundError is class belongs to a missing JAR file or JAR was not added into classpath or sometimes jar’s name has been changed by someone like in my case one of my colleagues has changed tibco.jar into tibco_v3.jar and the program is failing with java.lang.NoClassDefFoundError and I were wondering what’s wrong.

3. Just try to run with explicitly -classpath option with the classpath you think will work and if it’s working then it’s a sure short sign that someone is overriding java classpath.

4. Permission issue on JAR file can also cause NoClassDefFoundError in Java.
5. Typo on XML Configuration can also cause NoClassDefFoundError in Java.
6. when your compiled class which is defined in a package, doesn’t present in the same package while loading like in the case of JApplet it will throw NoClassDefFoundError in Java.

Possible Solutions:

1. The class is not available in Java Classpath.
2. If you are working in J2EE environment than the visibility of Class among multiple Classloader can also cause java.lang.NoClassDefFoundError, see examples and scenario section for detailed discussion.
3. Check for java.lang.ExceptionInInitializerError in your log file. NoClassDefFoundError due to the failure of static initialization is quite common.
4. Because NoClassDefFoundError is a subclass of java.lang.LinkageError it can also come if one of it dependency like native library may not available.
5. Any start-up script is overriding Classpath environment variable.
6. You might be running your program using jar command and class was not defined in manifest file’s ClassPath attribute.

Resources:

3 ways to solve NoClassDefFoundError

java.lang.NoClassDefFoundError Problem patterns

answered Aug 10, 2016 at 17:16

I have found that sometimes I get a NoClassDefFound error when code is compiled with an incompatible version of the class found at runtime. The specific instance I recall is with the apache axis library. There were actually 2 versions on my runtime classpath and it was picking up the out of date and incompatible version and not the correct one, causing a NoClassDefFound error. This was in a command line app where I was using a command similar to this.

set classpath=%classpath%;axis.jar

I was able to get it to pick up the proper version by using:

set classpath=axis.jar;%classpath%;

answered Aug 29, 2008 at 15:06

One interesting case in which you might see a lot of NoClassDefFoundErrors is when you:

1. throw a RuntimeException in the static block of your class Example
2. Intercept it (or if it just doesn’t matter like it is thrown in a test case)
3. Try to create an instance of this class Example

static class Example {
    static {
        thisThrowsRuntimeException();
    }
}

static class OuterClazz {

    OuterClazz() {
        try {
            new Example();
        } catch (Throwable ignored) { //simulating catching RuntimeException from static block
            // DO NOT DO THIS IN PRODUCTION CODE, THIS IS JUST AN EXAMPLE in StackOverflow
        }

        new Example(); //this throws NoClassDefFoundError
    }
}

NoClassDefError will be thrown accompanied with ExceptionInInitializerError from the static block RuntimeException.

This is especially important case when you see NoClassDefFoundErrors in your UNIT TESTS.

In a way you’re «sharing» the static block execution between tests, but the initial ExceptionInInitializerError will be just in one test case. The first one that uses the problematic Example class. Other test cases that use the Example class will just throw NoClassDefFoundErrors.

Ram PatraRam Patra

16k13 gold badges65 silver badges76 bronze badges

I was using Spring Framework with Maven and solved this error in my project.

There was a runtime error in the class. I was reading a property as integer, but when it read the value from the property file, its value was double.

Spring did not give me a full stack trace of on which line the runtime failed.
It simply said NoClassDefFoundError. But when I executed it as a native Java application (taking it out of MVC), it gave ExceptionInInitializerError which was the true cause and which is how I traced the error.

@xli’s answer gave me insight into what may be wrong in my code.

I get NoClassFoundError when classes loaded by the runtime class loader cannot access classes already loaded by the java rootloader. Because the different class loaders are in different security domains (according to java) the jvm won’t allow classes already loaded by the rootloader to be resolved in the runtime loader address space.

Run your program with ‘java -javaagent:tracer.jar [YOUR java ARGS]’

It produces output showing the loaded class, and the loader env that loaded the class. It’s very helpful tracing why a class cannot be resolved.

// ClassLoaderTracer.java
// From: https://blogs.oracle.com/sundararajan/entry/tracing_class_loading_1_5

import java.lang.instrument.*;
import java.security.*;

// manifest.mf
// Premain-Class: ClassLoadTracer

// jar -cvfm tracer.jar manifest.mf ClassLoaderTracer.class

// java -javaagent:tracer.jar  [...]

public class ClassLoadTracer 
{
    public static void premain(String agentArgs, Instrumentation inst) 
    {
        final java.io.PrintStream out = System.out;
        inst.addTransformer(new ClassFileTransformer() {
            public byte[] transform(ClassLoader loader, String className, Class classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer) throws IllegalClassFormatException {

                String pd = (null == protectionDomain) ? "null" : protectionDomain.getCodeSource().toString();
                out.println(className + " loaded by " + loader + " at " + new java.util.Date() + " in " + pd);

                // dump stack trace of the thread loading class 
                Thread.dumpStack();

                // we just want the original .class bytes to be loaded!
                // we are not instrumenting it...
                return null;
            }
        });
    }
}

answered Sep 9, 2015 at 12:02

yoAlex5yoAlex5

26.6k8 gold badges180 silver badges191 bronze badges

In case you have generated-code (EMF, etc.) there can be too many static initialisers which consume all stack space.

See Stack Overflow question How to increase the Java stack size?.

manuelvigarciamanuelvigarcia

1,3961 gold badge18 silver badges31 bronze badges

I fixed my problem by disabling the preDexLibraries for all modules:

dexOptions {
        preDexLibraries false
        ...

answered Feb 5, 2018 at 2:34

Ben WatersBen Waters

1471 silver badge8 bronze badges

logbasexlogbasex

1,3921 gold badge13 silver badges18 bronze badges

NoClassDefFoundError can also occur when a static initializer tries to load a resource bundle that is not available in runtime, for example a properties file that the affected class tries to load from the META-INF directory, but isn’t there. If you don’t catch NoClassDefFoundError, sometimes you won’t be able to see the full stack trace; to overcome this you can temporarily use a catch clause for Throwable:

try {
    // Statement(s) that cause(s) the affected class to be loaded
} catch (Throwable t) {
    Logger.getLogger("<logger-name>").info("Loading my class went wrong", t);
}

answered Sep 27, 2018 at 20:30

priyanka_raopriyanka_rao

4651 gold badge4 silver badges20 bronze badges

ST7ST7

2,1521 gold badge20 silver badges13 bronze badges

Brent BradburnBrent Bradburn

49.7k17 gold badges146 silver badges169 bronze badges

off99555off99555

3,5793 gold badges32 silver badges46 bronze badges

pixelpixel

8,90416 gold badges72 silver badges135 bronze badges

answered Jul 14, 2016 at 19:46

I got this message after removing two files from the SRC library, and when I brought them back I kept seeing this error message.

My solution was: Restart Eclipse. Since then I haven’t seen this message again