enabling org.jboss.ejb3 tracing causes ajuna error : The transaction is not active!

reply from Daniel Cullender in EJB 3.0 - View the full discussion

Hi Jaikiran, Thanks for the reply.


The transaction timeout is set to 600 seconds, and the amount of trace logging is not too excessive. The exception occurs the moment the mdb has finished processing the message which takes milliseconds.I agree it is quite strange, it must be some condition which is triggered off in trace mode (I have not had a chance to look at the source code yet)

Reply to this message by going to Community

Start a new discussion in EJB 3.0 at Community