My Oracle Support Banner

WebLogic Cluster Instance Fails to Start with 'java.lang.AssertionError: No replication server channel' when HTTP port is Disabled (Doc ID 1319381.1)

Last updated on FEBRUARY 26, 2018

Applies to:

Oracle Weblogic Server - Version 10.3 and later
Information in this document applies to any platform.

Symptoms

On WebLogic Server (WLS) Cluster configured with unicast and with the HTTP port disabled to allow only SSL traffic, instances fail to start logging the following error message:

<Error> <Cluster> <BEA-003111> <No channel exists for replication calls for cluster MgdSvr1>
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: No replication server channel for MgdSvr1
java.lang.AssertionError: No replication server channel for MgdSvr1
at weblogic.cluster.replication.ReplicationManagerServerRef.initialize(ReplicationManagerServerRef.java:120)
at weblogic.cluster.replication.ReplicationManagerServerRef.<clinit>(ReplicationManagerServerRef.java:83)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at weblogic.rmi.internal.BasicRuntimeDescriptor.getServerReferenceClass(BasicRuntimeDescriptor.java:469)
at weblogic.rmi.internal.BasicRuntimeDescriptor.createServerReference(BasicRuntimeDescriptor.java:426)
at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:195)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceRemote(RemoteObjectReplacer.java:120)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:103)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:241)
at weblogic.cluster.replication.ReplicationManager.start(ReplicationManager.java:245)
at weblogic.cluster.replication.ReplicationService.start(ReplicationService.java:28)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

Cause

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
Symptoms
Cause
Solution
References

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