WSM Server And WSM-PM Application Is No Starting After Upgrading From 12.2.1.0 to 12.2.1.4 (Doc ID 2765386.1)

Last updated on FEBRUARY 06, 2024

Applies to:

Symptoms

After upgrading SOA/OSB to 12.2.1.4, OWSM managed server fails to start with the below errors:

ERROR
-----------------------

<Error> <Deployer> <> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149231> <Unable to set the activation state to true for the application "wsm-pm".
weblogic.application.ModuleException: java.lang.NoClassDefFoundError: Could not initialize class org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
at weblogic.work.ContextWrap.run(ContextWrap.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:681)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
Caused By: java.lang.NoClassDefFoundError: Could not initialize class org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at org.apache.xerces.impl.dv.ObjectFactory.newInstance(Unknown Source)
at org.apache.xerces.impl.dv.SchemaDVFactory.getInstance(Unknown Source)
at org.apache.xerces.impl.dv.SchemaDVFactory.getInstance(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.reset(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source)
at com.tangosol.run.xml.SaxParser.validateXsd(SaxParser.java:265)
at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:223)
at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:83)
at com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:209)
at oracle.mds.internal.cache.coherence.CoherenceCache.<init>(CoherenceCache.java:116)
at oracle.mds.internal.cache.coherence.CoherenceCacheProvider.<init>(CoherenceCacheProvider.java:59)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Start a server with the wsm-pm application targeted to it using the startManagedWeblogic command

Cause

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