weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary ]

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 1734651660520697017 but it is not the secondary ]
via Oracle Community by 3004, 1 year ago
update found 18025409156064890 52 but it is not the secondary] at java.lang.Throwable.<init>(Compiled Code) at java.lang.Error.<init>(Compiled Code) at weblogic.utils.NestedError.<init>(Compiled Code)
via Oracle Community by 3004, 4 months ago
update found 4914721597745256666 but it is not the secondary ]
via Oracle Community by 3004, 4 months ago
update found 4914721597745256666 but it is not the secondary ]
via Oracle Community by 3004, 1 year ago
update found -5050872662681587012 but it is not the secondary at weblogic.rmi.extensions.BasicRequest.sendReceive(Compiled Code) at weblogic.cluster.replication.ReplicationManager_WLStub.update(Compiled Code) at weblogic.cluster.replication.ReplicationManager.updateSecondary(Compiled Code)
weblogic.cluster.replication.BadStatusException: update found 1734651660520697017 but it is not the secondary ]
at weblogic.servlet.internal.session.ReplicatedSession.sync(ReplicatedSession.java:371)
at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:59)
at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1198)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.