The "Bad version number in .class" error is displayed when performing operation verification for EJB, Web, or similar applications.
[Symptom]
An error message is displayed during EJB or Web application operation verification.
The following is an example of Web application operation verification, but errors are output to the server log in a similar way for EJB applications:
HTTP Status 500 -
type
Exception report
message
description
The server encountered an internal error () that prevented it from > fulfilling this request.
exception
javax.servlet.ServletException: JSVLT52352: Error during servlet instance allocation
root cause
java.lang.UnsupportedClassVersionError: Bad version number in .class > file |
[Cause]
The cause is that the JDK/JRE version of the server performing operation verification is an older version than the [Compiler compliance level] of the [Java Compiler] used for the build. Example: The JDK conformance level is 1.6 and the server JDK/JRE version is 1.5.
[Action]
Make the [Compiler compliance level] of the [Java Compiler] and the JDK/JRE version on the server performing operation verification the same, or perform the build in the older environment and perform operation verification again.
