weblogic.cluster.replication.BadStatusException: update found 5094537658943007368 >> but it is not the secondary

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Urgent!Error In Cluster Environment.
    via by 3004,
  • Fail-over in 2-server cluster
    via by 3004,
  • BadStatus exception
    via by 3004,
  • BadStatusException during heavy load
    via by 3004,
    • weblogic.cluster.replication.BadStatusException: update found 5094537658943007368 >> but it is not the secondary at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76) at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:181) at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:700) at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:433) at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:75) at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1332) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:959) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879) at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269) at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365) at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    No Bugmate found.