"Bad version number" in Java SDK

dwhytock — Mon, 11 Feb 2013 20:09:14 GMT

Hi...I'm getting the following stacktrace with my code:

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at splunktest.main(splunktest.java:23)

Line 23 in my code is:

    ServiceArgs serviceargs = new ServiceArgs();

Using Java 6 on WinXP.

Any ideas?

Re: "Bad version number" in Java SDK

dwhytock — Mon, 11 Feb 2013 20:50:01 GMT

The answer is, the SDK requires Java 6, while my office is still standardized on Java 5. Setting my program to run under Java 6 in Eclipse works fine.

Re: "Bad version number" in Java SDK

Damien_Dallimor — Wed, 13 Feb 2013 02:02:40 GMT

Yes it does. And there are also core XML classes used that were only introduced in version 6.

topic Re: "Bad version number" in Java SDK in Splunk Dev

"Bad version number" in Java SDK

Re: "Bad version number" in Java SDK

Re: "Bad version number" in Java SDK