"wolfc" wrote : | We then should resume the suspended tx. Oh bugrit, this will get complicated with the tidy up hack in there. What do we do if we have a suspended and a 'wrong' tx? Are you talking about | // Suspend any bad transaction - there is bug somewhere, but we will try to tidy things up | if (currentTx != null && currentTx.equals(transaction) == false) | { | log.warn("Current transaction " + currentTx + " is not the expected transaction."); | tm.suspend(); | tm.resume(transaction); | } | The log message should really be something like: | log.warn("SOMEBODY HAS PLAYING WITH THINGS THEY DON"T UNDERSTAND!"); | So there are more serious problems anyway. This has nothing to do with the endpoint's state so there is no need to invalidate it. A rollback exception when you attempt commit() is expected e.g. optimistic failure in the database, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109905#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...