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 unable to find > object -4723387961832123705 > at > weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76) > at > weblogic.cluster.replication.ReplicationManager_WLStub.remove(ReplicationMan > ager_WLStub.java:139) > at
weblogic.cluster.replication.NotFoundException: remove unable to find
> object -4723387961832123705
> at
>
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
> at
>
weblogic.cluster.replication.ReplicationManager_WLStub.remove(ReplicationMan
> ager_WLStub.java:139)
> at
>
weblogic.cluster.replication.ReplicationManager.unregister(ReplicationManage
> r.java:622)
> at
>
weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
> sion.java:255)
> at
>
weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession
> (ReplicatedSessionContext.java:116)
> at
>
weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
> teSessions(SessionContext.java:468)
> at
>
weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
> SessionContext.java:447)
> at
>
weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
> er.java:197)
> at
>
weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
> :191)
> at
weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:62)
>	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)