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
remove found 683 but it is not the secondary
via Oracle Community by 3004, 6 months ago
update found 4914721597745256666 but it is not the secondary
via Oracle Community by 3004, 6 months ago
update found 4914721597745256666 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 5094537658943007368 but it is not the secondary
via Oracle Community by 3004, 1 year ago
update found 1734651660520697017 but it is not the secondary
weblogic.cluster.replication.BadStatusException: remove found 683 but it is not the
secondary	at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)	at weblogic.cluster.replication.ReplicationManager_WLStub.remove(ReplicationManager_WLStub.java:139)	at weblogic.cluster.replication.ReplicationManager.unregister(ReplicationManager.java:680)	at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:320)	at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:213)	at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:523)	at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:491)	at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:209)	at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:203)	at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)