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
unregister unable to find object -7395851086118461928
via Oracle Community by 3004, 1 year ago
unregister unable to find object 1549818748307493344
via ypcorp.com by Unknown author, 1 year ago
unregister unable to find object           1549818748307493344
via Oracle Community by 3004, 6 months ago
unregister >unable >> to find object -6684186273746510374 >>
via Oracle Community by 3004, 1 year ago
getSecondaryJVMID unable to find object 9003606460390254419
weblogic.cluster.replication.NotFoundException: unregister unable
to find object -6684186273746510374	at weblogic.cluster.replication.ReplicationManager.find(ReplicationManager.java:596)	at weblogic.cluster.replication.ReplicationManager.unregister(ReplicationManager.java:644)	at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:259)	at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:131)	at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:502)	at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:479)	at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)	at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)	at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)