OC4J Instance Fails To Start With Error "Bad version number in .class file" After JDBC Driver Was Upgraded
(Doc ID 2051123.1)
Last updated on FEBRUARY 14, 2025
Applies to:
Oracle Containers for J2EE - Version 10.1.3.5.0 and laterInformation in this document applies to any platform.
Symptoms
After configuring one of the OC4J instances in OracleAS 10.1.3.5 to use newer JDBC driver version 11.2.0.4 according to <Note:420303.1> How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container,
the instance fails to start up with error:
-------- 15/08/19 11:43:34 Start process -------- 15/08/19 11:44:00 WARNING: Application.setConfig Application: default is in failed state as initialization failed. oracle.classloader.util.AnnotatedClassFormatError: Bad version number in .class file Invalid class: oracle.jdbc.pool.OracleDataSource Loader: oracle.jdbc:11.2.0.4 Code-Source: <ORACLE_HOME>/j2ee/<OC4JINSTANCENAME>/shared-lib/oracle.jdbc/11.2.0.4/ojdbc6.jar Configuration: in <ORACLE_HOME>/j2ee/<OC4JINSTANCENAME>/config/server.xml Dependent class: oracle.oc4j.sql.config.DataSourceConfigUtils Loader: oc4j:10.1.3 Code-Source: <ORACLE_HOME>/j2ee/home/lib/oc4j-internal.jar Configuration: in META-INF/boot.xml in <ORACLE_HOME>/j2ee/home/oc4j.jar 15/08/19 11:44:00 Error initializing server: Application: default is in failed state as initialization failed
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |