Symptom:
A MultiException has 6 exceptions. They are:
1. java.lang.AssertionError: Cannot export non clusterable object with jndiName:weblogic.jndi.internal.RootNamingNode@69f01d6c:
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.jndi.internal.RemoteNamingService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.management.mbeanservers.runtime.internal.RuntimeServerService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.mbeanservers.runtime.internal.RuntimeServerService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cacheprovider.CacheProviderServerService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cacheprovider.CacheProviderServerService
Cause:
This issue is caused by entry of the following JAVA_OPTIONS parameter ‘-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory’ when deploying into WebLolgic 12c. In WebLogic 12c, the built-in WebLogic Server XML Input factory implementation class is com.ctc.wstx.stax.WstxInputFactory, and the XML Factory Input should be set to this value. Due to a documentation bug, the manual deployment guide for P6 is still referencing the 11g implementation class, causing the reported issue to occur.
Fix:
Edit setDomainEnv.sh
Locate the line:
JAVA_OPTIONS at the end (added by the installer)
Change it to:
export JAVA_OPTIONS=”-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Doracle.jdbc.V8Compatible=true ${JAVA_OPTIONS}”
Reference Doc:
MOS Document ID: WebLogic 12c Managed Server Fails To Start When Passing The “-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory” Java Argument (Doc ID 2003152.1)