My Oracle Support Banner

[WLS 9.2.3] Can't start server when I use java 1.6.x, either jRockit's or Sun's JVM. (Doc ID 980620.1)

Last updated on OCTOBER 11, 2018

Applies to:

Oracle JRockit - Version: R27.6 and later   [Release: JRockit and later ]
Information in this document applies to any platform.


Customer said: "I didn't modify my custom startup script. I simply set the JAVA_HOME variable to either version 1.5 or version 1.6. So if I point the JAVA_HOME to v1.5, then the admin server and managed instance start up fine.
However if I point the JAVA_HOME to v1.6, then the start up failed, right after it displays the "STARTING" status":

<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: Provider could not be instantiated: java.lang.InstantiationException Provider could not be instantiated: java.lang.InstantiationException
at weblogic.application.descriptor.BasicMunger2.<clinit>(
at weblogic.application.ApplicationDescriptor$MyApplicationDescriptor.createXMLStreamReader(
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(
Truncated. see log file for complete stacktrace
<2009.12.14 23:03:46 UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>




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

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