#112 JavaNativeException

[Marc Logemann]

I am getting Bad Version in class file even though i have defined Java 1.6 as default JVM in the java prefs on Mac OS X. This error results in browser crashes as soon as i enter a java applet based site. Affects camino and firefox.

01.02.10 20:39:49 Camino[34545] java.lang.UnsupportedClassVersionError: Bad version number in .class file
at jep.AppletHandlerFactory.callRegisterNatives(Native Method)
at jep.AppletHandlerFactory.initProperties(Unknown Source)

01.02.10 20:39:49 Camino[34545] *** Terminating app due to uncaught exception 'JavaNativeException', reason: 'java.lang.UnsupportedClassVersionError: Bad version number in .class file'
*** Call stack at first throw:
(
0 CoreFoundation 0x96a9540a __raiseError + 410
1 libobjc.A.dylib 0x973f9509 objc_exception_throw + 56
2 CoreFoundation 0x96adfa21 -[NSException raise] + 17
3 JavaPluginCocoa 0x195f08ce registerNatives + 129
4 JavaEmbeddingPlugin 0x18a5cb86 Java_callRegisterNatives + 284
5 ??? 0x20da19b1 0x0 + 551164337
)

01.02.10 20:39:50 com.apple.launchd.peruser.501[262] ([0x0-0x42c42c].org.mozilla.camino[34545]) Exited with exit code: 6

[Steven Michaud]

What's your OS X version?

If it's 10.6.X, have you messed with your JVM along these lines --
http://tedwise.com/2009/09/25/using-java-1-5-and-java-1-4-on-snow-leopard/?

What verson of Firefox are you using, bundling which version of the
JEP?

[Marc Logemann]

Mac OS X 10.6.2 with Firefox download from today (just to be sure its not a broken Firefox or something). Latest JEP bundled with that as to what i can see. Most likely i have messed up Java because i am developing java apps and have done manually some things to get things in place after 10.6 migration. Apple really sucks big time with their OS X upgrade mechanism wrt to java.

Will try your link. Thanks for that.

[Marc Logemann]

I have applied all the stuff that the link suggested but without any difference....

[Steven Michaud]

> http://tedwise.com/2009/09/25/using-java-1-5-and-java-1-4-on-snow-leopard/

This link wasn't a recommendation. I was just trying to find out if
you had messed with (or messed up) your JVM along these lines.
Apparently you had ... even before you saw the link.

Doing that isn't supported, and I'm afraid you're now on your own. If
you can't remember exactly what you did (and so can't reverse it by
hand), you may need to do a clean install of the whole OS to get
things back into working order.

That said, it *should* be possible to do something like what that link
recommended and do it correctly. In other words, it should be
possible to change those instructions so they work properly.

Once I have time, I'll look further into this matter. But this isn't
going to happen anytime soon.