2 Replies Latest reply on Jul 18, 2007 1:29 PM by Taj

    Unable to passivate due to ctx lock in JBoss-4.0.4GA

    Taj Newbie

      Hi,

      We are having loads of these errors in the logs in production after porting to JBoss4.0.4GA from JBoss3.2.3 :-

      2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48gb6cb-umb
      2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48fdejr-ukx
      2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48fdenp-ukz


      Loads of them.

      These are coming mostly after the afterCompletion() of the SFSB is called.

      Is it related to the following JBAS-979:-

      http://jira.jboss.com/jira/browse/JBAS-979

      But the above had been fixed in Jboss4.0.4GA and I am using the same.

      And once these start coming, the system becomes quite slow.

      Can anyone provide me any pointers or direct me to anything specific.