"mark.little(a)jboss.com" wrote : "huuskart" wrote : When a transaction timeout or some other unexpected situation occurs, the new JBoss transaction manager (in JBoss 4.2.1.GA) marks the transaction into state Status.STATUS_ROLLEDBACK. | | | | Have you read the transaction standards with which we comply? They make it very clear that on a timeout you MUST roll back the transaction. They also make it very clear that data consistency is very important for transaction systems. So any low-level system exception, for instance, should force the transaction to roll back. | My point was not at all to complain about the transaction getting rolled back. It is blindingly obvious that it must be rolled back. My point was that in BMT EJB code, seeing Status.STATUS_ROLLEDBACK is very puzzling, and even more so because you can't commit() nor rollback() the transaction (both throw an exception), nor can you call begin() on it again. "mark.little(a)jboss.com" wrote : You can always call suspend to remove the thread-to-transaction association. | No, I can't. In EJB code, all I have to work with is javax.transaction.UserTransaction, and it does not give me that kind of control (nor would I wish to see such controls in EJB session code). Sorry, I forgot to mention the version: I'm using JBoss AS 4.2.1.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163600#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...