1 Reply Latest reply on May 17, 2002 12:11 AM by 3004

    Unexpected error in HTTP session timeout callback

    3004
      5.1sp8
                
                This happens VERY frequently with light load in a 2-node cluster :
                (session timeout set to 60 minutes, nothing calls invalidate())
                
                Wed Oct 17 04:12:04 UTC 2001:<E> <HttpSessionContext> Unexpected error in HTTP session timeout callback
                weblogic.cluster.replication.NotFoundException: unregister unable to find object -7395851086118461928
                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)
                --------------- nested within: ------------------
                weblogic.utils.NestedError: Can't unregister an ROID that does not exist - with nested exception:
                [weblogic.cluster.replication.NotFoundException: unregister unable to find object -7395851086118461928]
                at weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSession.java:267)
                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)
                
                What does this exception mean?
                
                --
                Dimitri
                
        • 1. RE: Unexpected error in HTTP session timeout callback
          3004
          Dimitri,
                    
                    I'm sorry to say I don't have an answer to this question but the same problem. At least a similar problem. Our app has a cluster of 6 weblogic instances with 2 IIS servers. The timeout is set to 30 minutes but we frequently see this happening at less than 2 minutes....
                    
                    Anybody?
                    
                    Dave