weblogic.cluster.replication.NotFoundException

Unable to find -4586061907150107 694

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web93

  • via Oracle Community by 3004, 1 year ago
    Unable to find -4586061907150107 694
  • Unable to find 7621353391848408868
  • via Oracle Community by 3004, 2 weeks ago
    Unable to find -3251242320747737856
  • Stack trace

    • weblogic.cluster.replication.NotFoundException: Unable to find -4586061907150107 694 at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90) at weblogic.cluster.replication.ReplicationManager_WLStub.fetch(ReplicationManager_WLStub.java:114) at weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManager.java:512) at weblogic.cluster.replication.ReplicationManager.lookup(ReplicationManager.java:354) at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:166) at weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestImpl.java:1466) at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1298) at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:96) at weblogic.servlet.security.internal.BasicSecurityModule.checkA(BasicSecurityModule.java:46) at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:109) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1112) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.