Team Member Managed Server in Failed or Admin State and Deployment in Prepared State on Clustered Weblogic Environment With Error in Log: "Non-homogeneous deployment for replicated sessions is not allowed" (Doc ID 2368970.1)

Last updated on MARCH 09, 2018

Applies to:

Symptoms

When attempting to start the Team Member managed server in Weblogic the following error occurs in the Team Member Weblogic server log. The managed server is in an ADMIN state, and the p6tm deployment in a PREPARED state:

ERROR


weblogic.application.ModuleException: weblogic.management.DeploymentException: [HTTP Session:100083]The Web application: p6tmweb in application: p6tm [Version=16.2.11.0] has its PersistenceStoreType set to: replicated_if_clustered for HTTP sessions. However, the target list does not contain all members of cluster: P6TMWebCluster. Non-homogeneous deployment for replicated sessions is not allowed.
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:175)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:170)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:80)
at weblogic.work.ContextWrap.run(ContextWrap.java:40)
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: weblogic.management.DeploymentException: [HTTP Session:100083]The Web application: p6tmweb in application: p6tm [Version=16.2.11.0] has its PersistenceStoreType set to: replicated_if_clustered for HTTP sessions. However, the target list does not contain all members of cluster: P6TMWebCluster. Non-homogeneous deployment for replicated sessions is not allowed.
at weblogic.servlet.internal.session.TargetValidator.validateTargetting(TargetValidator.java:31)
at weblogic.servlet.internal.session.SessionContextFactoryImpl.createPersistentSessionContext(SessionContextFactoryImpl.java:109)
at weblogic.servlet.internal.session.SessionContextFactoryImpl.createSessionContext(SessionContextFactoryImpl.java:64)
at weblogic.servlet.internal.session.SessionContextFactoryImpl.createSessionContext(SessionContextFactoryImpl.java:43)
at weblogic.servlet.internal.WebAppServletContext.initSessionContext(WebAppServletContext.java:1116)
at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:353)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:391)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:1274)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:770)
at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:295)
at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:285)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:109)
... 8 more


STEPS

The issue can be reproduced at will with the following steps:
1. Set up a clustered environment with multiple servers for Team Member
2. See main Team Member server is in an Admin state, other servers are in a Running state
3. See deployments in a Prepared state
4. Check server logs ...C:\Oracle\Middleware\Oracle_Home\user_projects\domains\..\servers\TeamMember\logs

BUSINESS IMPACT

The issue has the following business impact:
Due to this issue, users cannot access the Team Member web page.

Changes

Cause

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