weblogic.cluster.replication.BadStatusException

update found 5094537658943007368 but it is not the secondary

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web8

  • via Unknown by 3004,
  • via Unknown by 3004,
  • Stack trace

    • 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)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.