Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
update found 5094537658943007368 but it is not the secondary
via Oracle Community by 3004, 1 year ago
update found 1734651660520697017 but it is not the secondary
via Oracle Community by 3004, 1 year ago
update found -4880488432641332656 but it is not the secondary
via Oracle Community by 3004, 1 year ago
update found -900293168394139608 but it is not the secondary
via Oracle Community by 3004, 11 months ago
update found 4914721597745256666 but it is not the secondary
weblogic.cluster.replication.BadStatusException: update found 5094537658943007368but 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)