During OEM Upgrade From 12c to 13c, AdminServer Failed to Start. Error: weblogic.application.ModuleException: java.lang.NoSuchMethodError: weblogic.servlet.internal.session.SessionContext.initialize (Doc ID 2400865.1)

Last updated on DECEMBER 16, 2023

Applies to:

Symptoms

Upgrade of OMS from 12.1.0.5 to 13.2 fails during the OMS Configuration screen by following document https://docs.oracle.com/cd/E73210_01/EMUPG/GUID-3E2CC73D-22BA-492B-8C59-E55E6B87F41D.htm#EMUPG165 

OEM 12.1.0.5 is build with WLS version - 10.3.6
OEM 13.2 is build with WLS version - 12.1.3

The OUI will upgrade the version in the background. The issue is seen related to WLS stack stating unable to connect (start) the WLS :

* Getting the following error in the ADMINSERVER.OUT :

<May 10, 2018 12:18:32 PM CDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "bea_wls_internal".
weblogic.application.ModuleException: java.lang.NoSuchMethodError: weblogic.servlet.internal.session.SessionContext.initialize(Lweblogic/servlet/internal/ServletWorkContext;)V
at weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodError: weblogic.servlet.internal.session.SessionContext.initialize(Lweblogic/servlet/internal/ServletWorkContext;)V
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:2868)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1648)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:805)
at weblogic.application.internal.ExtensibleModuleWrapper$ActivateStateChange.next(ExtensibleModuleWrapper.java:317)
at weblogic.application.internal.ExtensibleModuleWrapper$ActivateStateChange.next(ExtensibleModuleWrapper.java:313)
Truncated. see log file for complete stacktrace
>
<May 10, 2018 12:18:34 PM CDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.application.ModuleException: java.lang.NoSuchMethodError: weblogic.servlet.internal.session.SessionContext.initialize(Lweblogic/servlet/internal/ServletWorkContext;)V
at weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:61)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:145)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418)
at weblogic.management.deploy.internal.ConfiguredDeployments.deployPreStandbyInternalApps(ConfiguredDeployments.java:85)
at weblogic.management.deploy.internal.DeploymentServerService.deployPreStandbyInternalApps(DeploymentServerService.java:198)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:56)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017)
at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: java.lang.NoSuchMethodError: weblogic.servlet.internal.session.SessionContext.initialize(Lweblogic/servlet/internal/ServletWorkContext;)V
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:2868)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1648)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:805)
at weblogic.application.internal.ExtensibleModuleWrapper$ActivateStateChange.next(ExtensibleModuleWrapper.java:317)
at weblogic.application.internal.ExtensibleModuleWrapper$ActivateStateChange.next(ExtensibleModuleWrapper.java:313)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:121)
... 35 more

>
<May 10, 2018 12:18:34 PM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<May 10, 2018 12:18:35 PM CDT> <INFO> <NodeManager> <The server 'ADMINSERVER' with process id 6605 is no longer alive; waiting for the process to die.>
<May 10, 2018 12:18:35 PM CDT> <FINEST> <NodeManager> <Process died.>
<May 10, 2018 12:18:35 PM CDT> <INFO> <NodeManager> <Server failed during startup so will not be restarted>

* From NODEMANAGER.LOG :

<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Creating directory "path/user_projects/domains/Domain-Name/servers/ADMINSERVER/logs">
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Creating directory "path/user_projects/domains/Domain-Name/servers/ADMINSERVER/data/nodemanager">
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Creating directory "path/user_projects/domains/Domain-Name/servers/ADMINSERVER/tmp">
<May 10, 2018 12:18:17 PM CDT> <WARNING> <Domain-Name> <ADMINSERVER> <Startup config file path/user_projects/domains/Domain-Name/servers/ADMINSERVER/data/nodemanager/startup.properties for server 'Admin-Server-name' does not exist, and startup config properties are not specified when invoking start command. Node Manager will try its best to start the server using default configurations which may not fit and may lead to startup failure.>
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Server error log also redirected to server log>
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Starting WebLogic server with command line: path/user_projects/domains/Domain-Name/bin/startEMServer.sh >
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Working directory is 'path/user_projects/domains/Domain-Name'>
<May 10, 2018 12:18:17 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Server output log file is 'path/user_projects/domains/Domain-Name/servers/ADMINSERVER/logs/ADMINSERVER.out'>
<May 10, 2018 12:18:35 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <The server 'ADMINSERVER' with process id 6605 is no longer alive; waiting for the process to die.>
<May 10, 2018 12:18:35 PM CDT> <INFO> <Domain-Name> <ADMINSERVER> <Server failed during startup so will not be restarted>
<May 10, 2018 12:18:35 PM CDT> <WARNING> <Server start command for WebLogic server 'ADMINSERVER' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'ADMINSERVER' log for detailed information.> 

Changes

To test a manual restart of the AdminServer when we tried to run ./startWebLogic.sh, we found that the script was trying to call the commEnv.sh of old OEM 12c install which gave the clue to check the Environment variables.

Cause

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