Can't unregister an ROID that does not exist

Please use service pack 5.
          
          --
          Cheers - Wei
          
          
          
          Yogi Mudras <ymudras@microstrategy.com> wrote in message
          news:39abd52d$1@newsgroups.bea.com...
          > Hi
          >
          > We are using instate memory replication and during stress, we suddenly
          began
          > to get this error. We are wondering what could be the cause of this error
          ?
          > Has anyone seen this before ?
          >
          > Yogi
          >
          > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext> Unexpected error in
          > HTTP session timeout callback
          > 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)
          > --------------- nested within: ------------------
          > weblogic.utils.NestedError: Can't unregister an ROID that does not exist -
          > with nested exception:
          > [weblogic.cluster.replication.NotFoundException: remove unable to find
          > object -4723387961832123705]
          > at
          >
          weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          
          > sion.java:264)
          > 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)
          >
          >
          
          
          

We are using SP 5 on Win NT.
          
          
          "Wei Guan" <wei.guan@beasys.com> wrote in message
          news:39b1d12d@newsgroups.bea.com...
          > Please use service pack 5.
          >
          > --
          > Cheers - Wei
          >
          >
          >
          > Yogi Mudras <ymudras@microstrategy.com> wrote in message
          > news:39abd52d$1@newsgroups.bea.com...
          > > Hi
          > >
          > > We are using instate memory replication and during stress, we suddenly
          > began
          > > to get this error. We are wondering what could be the cause of this
          error
          > ?
          > > Has anyone seen this before ?
          > >
          > > Yogi
          > >
          > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext> Unexpected error
          in
          > > HTTP session timeout callback
          > > 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)
          > > --------------- nested within: ------------------
          > > weblogic.utils.NestedError: Can't unregister an ROID that does not
          exist -
          > > with nested exception:
          > > [weblogic.cluster.replication.NotFoundException: remove unable to find
          > > object -4723387961832123705]
          > > at
          > >
          >
          weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          >
          > > sion.java:264)
          > > 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)
          > >
          > >
          >
          >
          
          
          

Typically you should be too concerned about this. But out of curiosity, what's
          the load on the servers and could you more information about your setup
          including the heap size you were using etc.
          
          Thanks
          
          - Prasad
          
          Yogi Mudras wrote:
          
          > We are using SP 5 on Win NT.
          >
          > "Wei Guan" <wei.guan@beasys.com> wrote in message
          > news:39b1d12d@newsgroups.bea.com...
          > > Please use service pack 5.
          > >
          > > --
          > > Cheers - Wei
          > >
          > >
          > >
          > > Yogi Mudras <ymudras@microstrategy.com> wrote in message
          > > news:39abd52d$1@newsgroups.bea.com...
          > > > Hi
          > > >
          > > > We are using instate memory replication and during stress, we suddenly
          > > began
          > > > to get this error. We are wondering what could be the cause of this
          > error
          > > ?
          > > > Has anyone seen this before ?
          > > >
          > > > Yogi
          > > >
          > > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext> Unexpected error
          > in
          > > > HTTP session timeout callback
          > > > 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)
          > > > --------------- nested within: ------------------
          > > > weblogic.utils.NestedError: Can't unregister an ROID that does not
          > exist -
          > > > with nested exception:
          > > > [weblogic.cluster.replication.NotFoundException: remove unable to find
          > > > object -4723387961832123705]
          > > > at
          > > >
          > >
          > weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          > >
          > > > sion.java:264)
          > > > 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)
          > > >
          > > >
          > >
          > >
          
          

          We are running into this as well. We are trying to debug a problem
          where a person was able to grab the session of another user. Our
          first guess is that this is an application issue. However, I would
          like to be able to rule out this error as a problem. Can someone
          explain what causes this problem and whether it affects session
          data.
          
          We are using WLS 5.1 SP8 on Solaris 2.7. Additionally, we have
          installed Open Market on top of WLS.
          
          
          Thanks,
          Alex
          
          Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >Typically you should be too concerned about this. But
          >out of curiosity, what's
          >the load on the servers and could you more information
          >about your setup
          >including the heap size you were using etc.
          >
          >Thanks
          >
          >- Prasad
          >
          >Yogi Mudras wrote:
          >
          >> We are using SP 5 on Win NT.
          >>
          >> "Wei Guan" <wei.guan@beasys.com> wrote in message
          >> news:39b1d12d@newsgroups.bea.com...
          >> > Please use service pack 5.
          >> >
          >> > --
          >> > Cheers - Wei
          >> >
          >> >
          >> >
          >> > Yogi Mudras <ymudras@microstrategy.com> wrote in message
          >> > news:39abd52d$1@newsgroups.bea.com...
          >> > > Hi
          >> > >
          >> > > We are using instate memory replication and during
          >stress, we suddenly
          >> > began
          >> > > to get this error. We are wondering what could be
          >the cause of this
          >> error
          >> > ?
          >> > > Has anyone seen this before ?
          >> > >
          >> > > Yogi
          >> > >
          >> > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext>
          >Unexpected error
          >> in
          >> > > HTTP session timeout callback
          >> > > 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)
          >> > > --------------- nested within: ------------------
          >> > > weblogic.utils.NestedError: Can't unregister an
          >ROID that does not
          >> exist -
          >> > > with nested exception:
          >> > > [weblogic.cluster.replication.NotFoundException:
          >remove unable to find
          >> > > object -4723387961832123705]
          >> > > at
          >> > >
          >> >
          >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          >> >
          >> > > sion.java:264)
          >> > > 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)
          >> > >
          >> > >
          >> >
          >> >
          >
          
          

It should never be possible for one user to grab session of another user.
          
          So, while the trigger is trying to cleanup session's it calls the secondary server
          and asks it to remove the object. In this case, the object is already gone for some
          reason. Since the intention is to clean the session, it is safe to ignore the
          message.
          
          -- Prasad
          
          Alex Metcalf wrote:
          
          > We are running into this as well. We are trying to debug a problem
          > where a person was able to grab the session of another user. Our
          > first guess is that this is an application issue. However, I would
          > like to be able to rule out this error as a problem. Can someone
          > explain what causes this problem and whether it affects session
          > data.
          >
          > We are using WLS 5.1 SP8 on Solaris 2.7. Additionally, we have
          > installed Open Market on top of WLS.
          >
          > Thanks,
          > Alex
          >
          > Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          > >Typically you should be too concerned about this. But
          > >out of curiosity, what's
          > >the load on the servers and could you more information
          > >about your setup
          > >including the heap size you were using etc.
          > >
          > >Thanks
          > >
          > >- Prasad
          > >
          > >Yogi Mudras wrote:
          > >
          > >> We are using SP 5 on Win NT.
          > >>
          > >> "Wei Guan" <wei.guan@beasys.com> wrote in message
          > >> news:39b1d12d@newsgroups.bea.com...
          > >> > Please use service pack 5.
          > >> >
          > >> > --
          > >> > Cheers - Wei
          > >> >
          > >> >
          > >> >
          > >> > Yogi Mudras <ymudras@microstrategy.com> wrote in message
          > >> > news:39abd52d$1@newsgroups.bea.com...
          > >> > > Hi
          > >> > >
          > >> > > We are using instate memory replication and during
          > >stress, we suddenly
          > >> > began
          > >> > > to get this error. We are wondering what could be
          > >the cause of this
          > >> error
          > >> > ?
          > >> > > Has anyone seen this before ?
          > >> > >
          > >> > > Yogi
          > >> > >
          > >> > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext>
          > >Unexpected error
          > >> in
          > >> > > HTTP session timeout callback
          > >> > > 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)
          > >> > > --------------- nested within: ------------------
          > >> > > weblogic.utils.NestedError: Can't unregister an
          > >ROID that does not
          > >> exist -
          > >> > > with nested exception:
          > >> > > [weblogic.cluster.replication.NotFoundException:
          > >remove unable to find
          > >> > > object -4723387961832123705]
          > >> > > at
          > >> > >
          > >> >
          > >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          > >> >
          > >> > > sion.java:264)
          > >> > > 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)
          > >> > >
          > >> > >
          > >> >
          > >> >
          > >
          
          

          Shouldn't the trigger be removed when the session is invalidated?
          
          This is very ugly in the log files - makes hard for us to find
          other problems. It would be really, really nice to to see it.
          
          Mike
          
          
          Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >It should never be possible for one user to grab session
          >of another user.
          >
          >So, while the trigger is trying to cleanup session's it
          >calls the secondary server
          >and asks it to remove the object. In this case, the object
          >is already gone for some
          >reason. Since the intention is to clean the session, it
          >is safe to ignore the
          >message.
          >
          >-- Prasad
          >
          >Alex Metcalf wrote:
          >
          >> We are running into this as well. We are trying to
          >debug a problem
          >> where a person was able to grab the session of another
          >user. Our
          >> first guess is that this is an application issue. However,
          >I would
          >> like to be able to rule out this error as a problem.
          >Can someone
          >> explain what causes this problem and whether it affects
          >session
          >> data.
          >>
          >> We are using WLS 5.1 SP8 on Solaris 2.7. Additionally,
          >we have
          >> installed Open Market on top of WLS.
          >>
          >> Thanks,
          >> Alex
          >>
          >> Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >> >Typically you should be too concerned about this. But
          >> >out of curiosity, what's
          >> >the load on the servers and could you more information
          >> >about your setup
          >> >including the heap size you were using etc.
          >> >
          >> >Thanks
          >> >
          >> >- Prasad
          >> >
          >> >Yogi Mudras wrote:
          >> >
          >> >> We are using SP 5 on Win NT.
          >> >>
          >> >> "Wei Guan" <wei.guan@beasys.com> wrote in message
          >> >> news:39b1d12d@newsgroups.bea.com...
          >> >> > Please use service pack 5.
          >> >> >
          >> >> > --
          >> >> > Cheers - Wei
          >> >> >
          >> >> >
          >> >> >
          >> >> > Yogi Mudras <ymudras@microstrategy.com> wrote in
          >message
          >> >> > news:39abd52d$1@newsgroups.bea.com...
          >> >> > > Hi
          >> >> > >
          >> >> > > We are using instate memory replication and during
          >> >stress, we suddenly
          >> >> > began
          >> >> > > to get this error. We are wondering what could
          >be
          >> >the cause of this
          >> >> error
          >> >> > ?
          >> >> > > Has anyone seen this before ?
          >> >> > >
          >> >> > > Yogi
          >> >> > >
          >> >> > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext>
          >> >Unexpected error
          >> >> in
          >> >> > > HTTP session timeout callback
          >> >> > > 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)
          >> >> > > --------------- nested within: ------------------
          >> >> > > weblogic.utils.NestedError: Can't unregister
          >an
          >> >ROID that does not
          >> >> exist -
          >> >> > > with nested exception:
          >> >> > > [weblogic.cluster.replication.NotFoundException:
          >> >remove unable to find
          >> >> > > object -4723387961832123705]
          >> >> > > at
          >> >> > >
          >> >> >
          >> >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          >> >> >
          >> >> > > sion.java:264)
          >> >> > > 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)
          >> >> > >
          >> >> > >
          >> >> >
          >> >> >
          >> >
          >
          
          

Probably we should squelch the exception in this case.
          
          -- Prasad
          
          Mike Reiche wrote:
          
          > Shouldn't the trigger be removed when the session is invalidated?
          >
          > This is very ugly in the log files - makes hard for us to find
          > other problems. It would be really, really nice to to see it.
          >
          > Mike
          >
          > Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          > >It should never be possible for one user to grab session
          > >of another user.
          > >
          > >So, while the trigger is trying to cleanup session's it
          > >calls the secondary server
          > >and asks it to remove the object. In this case, the object
          > >is already gone for some
          > >reason. Since the intention is to clean the session, it
          > >is safe to ignore the
          > >message.
          > >
          > >-- Prasad
          > >
          > >Alex Metcalf wrote:
          > >
          > >> We are running into this as well. We are trying to
          > >debug a problem
          > >> where a person was able to grab the session of another
          > >user. Our
          > >> first guess is that this is an application issue. However,
          > >I would
          > >> like to be able to rule out this error as a problem.
          > >Can someone
          > >> explain what causes this problem and whether it affects
          > >session
          > >> data.
          > >>
          > >> We are using WLS 5.1 SP8 on Solaris 2.7. Additionally,
          > >we have
          > >> installed Open Market on top of WLS.
          > >>
          > >> Thanks,
          > >> Alex
          > >>
          > >> Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          > >> >Typically you should be too concerned about this. But
          > >> >out of curiosity, what's
          > >> >the load on the servers and could you more information
          > >> >about your setup
          > >> >including the heap size you were using etc.
          > >> >
          > >> >Thanks
          > >> >
          > >> >- Prasad
          > >> >
          > >> >Yogi Mudras wrote:
          > >> >
          > >> >> We are using SP 5 on Win NT.
          > >> >>
          > >> >> "Wei Guan" <wei.guan@beasys.com> wrote in message
          > >> >> news:39b1d12d@newsgroups.bea.com...
          > >> >> > Please use service pack 5.
          > >> >> >
          > >> >> > --
          > >> >> > Cheers - Wei
          > >> >> >
          > >> >> >
          > >> >> >
          > >> >> > Yogi Mudras <ymudras@microstrategy.com> wrote in
          > >message
          > >> >> > news:39abd52d$1@newsgroups.bea.com...
          > >> >> > > Hi
          > >> >> > >
          > >> >> > > We are using instate memory replication and during
          > >> >stress, we suddenly
          > >> >> > began
          > >> >> > > to get this error. We are wondering what could
          > >be
          > >> >the cause of this
          > >> >> error
          > >> >> > ?
          > >> >> > > Has anyone seen this before ?
          > >> >> > >
          > >> >> > > Yogi
          > >> >> > >
          > >> >> > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext>
          > >> >Unexpected error
          > >> >> in
          > >> >> > > HTTP session timeout callback
          > >> >> > > 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)
          > >> >> > > --------------- nested within: ------------------
          > >> >> > > weblogic.utils.NestedError: Can't unregister
          > >an
          > >> >ROID that does not
          > >> >> exist -
          > >> >> > > with nested exception:
          > >> >> > > [weblogic.cluster.replication.NotFoundException:
          > >> >remove unable to find
          > >> >> > > object -4723387961832123705]
          > >> >> > > at
          > >> >> > >
          > >> >> >
          > >> >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          > >> >> >
          > >> >> > > sion.java:264)
          > >> >> > > 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)
          > >> >> > >
          > >> >> > >
          > >> >> >
          > >> >> >
          > >> >
          > >
          
          

          When can we expect this to be taken care of?
          This exception fills our logs everyday. Will this be in an upcomming service pack?
          
          --Michael
          
          Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >Probably we should squelch the exception in this case.
          >
          >-- Prasad
          >
          >Mike Reiche wrote:
          >
          >> Shouldn't the trigger be removed when the session is invalidated?
          >>
          >> This is very ugly in the log files - makes hard for us to find
          >> other problems. It would be really, really nice to to see it.
          >>
          >> Mike
          >>
          >> Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >> >It should never be possible for one user to grab session
          >> >of another user.
          >> >
          >> >So, while the trigger is trying to cleanup session's it
          >> >calls the secondary server
          >> >and asks it to remove the object. In this case, the object
          >> >is already gone for some
          >> >reason. Since the intention is to clean the session, it
          >> >is safe to ignore the
          >> >message.
          >> >
          >> >-- Prasad
          >> >
          >> >Alex Metcalf wrote:
          >> >
          >> >> We are running into this as well. We are trying to
          >> >debug a problem
          >> >> where a person was able to grab the session of another
          >> >user. Our
          >> >> first guess is that this is an application issue. However,
          >> >I would
          >> >> like to be able to rule out this error as a problem.
          >> >Can someone
          >> >> explain what causes this problem and whether it affects
          >> >session
          >> >> data.
          >> >>
          >> >> We are using WLS 5.1 SP8 on Solaris 2.7. Additionally,
          >> >we have
          >> >> installed Open Market on top of WLS.
          >> >>
          >> >> Thanks,
          >> >> Alex
          >> >>
          >> >> Prasad Peddada <prasadp@bgnet.bgsu.edu> wrote:
          >> >> >Typically you should be too concerned about this. But
          >> >> >out of curiosity, what's
          >> >> >the load on the servers and could you more information
          >> >> >about your setup
          >> >> >including the heap size you were using etc.
          >> >> >
          >> >> >Thanks
          >> >> >
          >> >> >- Prasad
          >> >> >
          >> >> >Yogi Mudras wrote:
          >> >> >
          >> >> >> We are using SP 5 on Win NT.
          >> >> >>
          >> >> >> "Wei Guan" <wei.guan@beasys.com> wrote in message
          >> >> >> news:39b1d12d@newsgroups.bea.com...
          >> >> >> > Please use service pack 5.
          >> >> >> >
          >> >> >> > --
          >> >> >> > Cheers - Wei
          >> >> >> >
          >> >> >> >
          >> >> >> >
          >> >> >> > Yogi Mudras <ymudras@microstrategy.com> wrote in
          >> >message
          >> >> >> > news:39abd52d$1@newsgroups.bea.com...
          >> >> >> > > Hi
          >> >> >> > >
          >> >> >> > > We are using instate memory replication and during
          >> >> >stress, we suddenly
          >> >> >> > began
          >> >> >> > > to get this error. We are wondering what could
          >> >be
          >> >> >the cause of this
          >> >> >> error
          >> >> >> > ?
          >> >> >> > > Has anyone seen this before ?
          >> >> >> > >
          >> >> >> > > Yogi
          >> >> >> > >
          >> >> >> > > Tue Aug 29 01:09:13 EDT 2000:<E> <HttpSessionContext>
          >> >> >Unexpected error
          >> >> >> in
          >> >> >> > > HTTP session timeout callback
          >> >> >> > > 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)
          >> >> >> > > --------------- nested within: ------------------
          >> >> >> > > weblogic.utils.NestedError: Can't unregister
          >> >an
          >> >> >ROID that does not
          >> >> >> exist -
          >> >> >> > > with nested exception:
          >> >> >> > > [weblogic.cluster.replication.NotFoundException:
          >> >> >remove unable to find
          >> >> >> > > object -4723387961832123705]
          >> >> >> > > at
          >> >> >> > >
          >> >> >> >
          >> >> >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(ReplicatedSes
          >> >> >> >
          >> >> >> > > sion.java:264)
          >> >> >> > > 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)
          >> >> >> > >
          >> >> >> > >
          >> >> >> >
          >> >> >> >
          >> >> >
          >> >
          >