When a (transactional) method of an EJB calls another (transactional) method of another EJB, and an exception is thrown in the second, but catched in the first one, it seems that the transaction is automatically rolled back when the second one returns, even if the first one catches it, is this true? how can I avoid it?
The scenario is the following one:
@Stateless
class ClassA {
@EJB
ClassB objectB;
methodA() {
try {
objectB.methodB();
}
catch(Exception e) {
//Here the transaction started in this method is
//automatically rolled back. Is this avoidable?
}
}
}
@Stateless
class ClassB {
methodB() throws Exception { throw new Exception() }
}
Best Answer
Transaction is rolled back in case you throw a
RuntimeException
or any Exception which have@ApplicationException
annotation withrollback
attribute set totrue
, so:will rollback the current transaction.
By default ApplicationException doesn't rollback your transaction.
If you don't want to methodB to rollback your transaction you can either change the rollback behavior of your
ApplicationException
or prevent the transaction sharing.The latter is achievable by changing the
TransactionAttribute
of methodB i.e. toRequiresNew
. Then methodA transaction (Tx1) will be suspendend and in case methodB throws an exception which results in rollback of its transaction (Tx2), you can still catch it in methodA and prevent rollback of your methodA transaction (Tx1).