My Oracle Support Banner

'Error initializing server: Application: default is in failed state as initialization failed' When Upgrading JDBC Version in Oracle Containers For J2EE 10.1.3.X (Doc ID 849050.1)

Last updated on MARCH 12, 2019

Applies to:

Oracle Containers for J2EE - Version 10.1.3.4.0 and later
JDBC - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 25-Aug-2011***


Symptoms

After upgrading JDBC driver version shipped with Oracle Application Server 10.1.3.x to JDBC driver version 10.2.0.4 by default per instructions in <Note 420303.1> How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container , the OC4J container fails to start.

OC4J log file shows: 

09/06/10 12:37:22 WARNING: Application.setConfig Application: default is in
failed state as initialization failed.
java.lang.NullPointerException
09/06/10 12:37:22 Error initializing server: Application: default is in failed
state as initialization failed
09/06/10 12:37:26 Fatal error: server exiting

 


09/06/24 01:22:27 WARNING: Application.setConfig Application: default is in failed state as initialization failed.
java.lang.InstantiationException: resource-provider class 'oracle.jms.OjmsContext' not found
09/06/24 01:22:27 Error initializing server: Application: default is in failed state as initialization failed
09/06/24 01:22:29 Fatal error: server exiting

Changes

Upgrade of JDBC driver version to 10.2.0.4.

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
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.