2 Replies Latest reply on Jan 27, 2005 6:04 PM by natebowler

    Unable to passivate due to ctx lock

    natebowler Newbie

      I've got a stateful session bean, and after using it, I see the folling messages repeated in the logs:

      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkkzl-8
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypklco-9
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkllu-a
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkm0b-c
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkm8n-d
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkmha-e
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkmp2-f
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkmwv-g
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx lock, id=e3ypkn7f-h
      WARN [AbstractInstanceCache.tryToPassivate()]: Unable t
      o passivate due to ctx lock, id=e3ypkneo-i

      The stateful session bean I am using is pretty straightforward, as is the use case.

      Could someone explain what this means and if there is anything I can do to avoid this warning?