weblogic.cluster.replication.BadStatusException

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.

  • Cluster Problem
    via by 3004,
  • Cluster Problem
    via by 3004,
    • weblogic.cluster.replication.BadStatusException: updateSecondary found >>4914721597745256666 but it is not the p >>rimary >> at >> >> > weblogic.cluster.replication.ReplicationManager.find(ReplicationManager.java > :598) > >> at >> >> > weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationM > anager.java:694) > >> at >> >> > weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.j > ava:433) > >> at >> >> > weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSe > ssionContext.java:75) > >> at >> >> > weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl. > java:1332) > >> at >> >> > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp > l.java:959) > >> at >> >> > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp > l.java:879) > >> at >> >> > weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext > Manager.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)SocketHTTP.java:253 > ) > >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    No Bugmate found.