2 Replies Latest reply on Aug 23, 2005 8:44 AM by Jason Cunningham

    Stateless session's remove() method being called during a tr

    Jason Cunningham Newbie

      Hi All,

      I'm seeing this problem very infrequently in my logs, but it does cause a problem each time it occurs, so I'd be grateful for any advice.

      I've got a stateless session bean that is configured to use BMT - which it normall does perfectly. Every now and again, I get this error:

      2005-08-19 00:00:17,606 ERROR [org.jboss.ejb.plugins.TxInterceptorBMT] Application error: BMT stateless bean *Stateless*Session should complete transactions before returning (ejb1.1 spec, 11.6.1)

      I can't see anyway that the code could exit without hitting a txn.commit(); type of statement.

      The interesting thing is that each occurence of the problem is followed by a notification of a '*Stateless*Session' being destroyed.

      My guess is that the container is passivating / destroying the session bean during the transaction. This makes sense given the error message. Question is, how can I get JBoss to respect the transaction and wait for it complete before nuking the bean.

      I'm running Jboss 3.2.6.

      Any ideas / advice?

      As always, thanks for your time.