0 Replies Latest reply on Jul 16, 2003 2:54 AM by Jan Radl

    Bean passivation problem

    Jan Radl Newbie

      Hallo all,

      I have a big problem with passivation of Stateful SessionBeans in JBoss 3.2.1. I would like to switch to JBoss from BES 5.2 but I cannot ressolve the folloving problem :

      I code one simple Stateful SessionBean Salary calling some methods on BMP EntityBean. On client I run several threads with Salary bean operations. The problem comes when the container try to passivate one of the SessionBean instance. Than I receive the folloving message in server.log:

      2003-07-15 21:30:58,423 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Attempting to passivate; ctx=org.jboss.ejb.StatefulSessionEnterpriseContext@1c69f7b
      2003-07-15 21:30:58,426 INFO [STDOUT] in passivate session id = org.jboss.ejb.StatefulSessionEnterpriseContext$StatefulSessionContextImpl@709366
      2003-07-15 21:30:58,426 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Saving session state to: /opt/jboss-3.2.1/server/fss/tmp/sessions/Salary-di6ayooz-9/di6az6mu-b.ser
      2003-07-15 21:30:58,427 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Writing session state: com.b1.SalaryEJB@46f6f0
      2003-07-15 21:30:58,432 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Passivation complete; ctx=org.jboss.ejb.StatefulSessionEnterpriseContext@1c69f7b
      2003-07-15 21:30:58,432 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=di6az6l4-a


      The same example works fine on BES 5.2. This is only one problem that is block our movement from BES to world number one J2EE Server.

      Thanl you for any help.

      Jan