java.lang.AssertionError: Found the session, but not the application. Double-check that proxy/loadbalancers are respecting session stickiness.

ICEsoft JIRA Issue Tracker | Jack Van Ooststroom | 7 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Application becomes unresponsive in clustered environment

    Oracle Community | 6 years ago | Jeets-Oracle
    java.lang.AssertionError: Found the session, but not the application. Double-check that proxy/loadbalancers are respecting session stickiness.
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.AssertionError

      Found the session, but not the application. Double-check that proxy/loadbalancers are respecting session stickiness.

      at weblogic.cluster.replication.ReplicationManager.update()
    2. weblogic.cluster.replication
      ReplicationManager_WLSkel.invoke
      1. weblogic.cluster.replication.ReplicationManager.update(ReplicationManager.java:836)
      2. weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source)
      2 frames
    3. weblogic.rmi.internal
      BasicServerRef$1.run
      1. weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
      2. weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
      2 frames
    4. weblogic.security.acl
      AuthenticatedSubject.doAs
      1. weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
      1 frame