weblogic.cluster.replication.BadStatusException: remove found 683 but it is not > the secondary]

Oracle Community | 3004 | 1 decade ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    HTTP session timeout callback and replication.BadStatusException

    Oracle Community | 1 decade ago | 3004
    weblogic.cluster.replication.BadStatusException: remove found 683 but it is not > the secondary]

    Root Cause Analysis

    1. weblogic.cluster.replication.BadStatusException

      remove found 683 but it is not > the secondary]

      at weblogic.servlet.internal.session.ReplicatedSession.invalidate()
    2. weblogic.servlet.internal
      SessionContext$SessionInvalidator.trigger
      1. weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:324)
      2. weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:213)
      3. weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalidateSessions(SessionContext.java:523)
      4. weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:491)
      4 frames
    3. weblogic.time.common
      ScheduledTrigger.execute
      1. weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:209)
      2. weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:203)
      2 frames
    4. weblogic.time.server
      ScheduledTrigger.execute
      1. weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
      1 frame
    5. weblogic.kernel
      ExecuteThread.run
      1. weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
      1 frame