TransactionImpleManager.suspend

[thomas_scheibelreiter]

Hi folks

I have bean using BMT. Another bean using BMT is injected into the first.

Now when the first one calls a method of the second one, suddenly the transaction is closed.

Here is the trace:

2018-11-23 12:15:32,275 +0100 [TRACE] [com.arjuna.ats.jta] (default task-18) TransactionImple.getStatus: javax.transaction.Status.STATUS_ACTIVE

2018-11-23 12:15:32,276 +0100 [TRACE] [com.arjuna.ats.jta] (default task-18) TransactionImpleManager.suspend

2018-11-23 12:15:32,277 +0100 [TRACE] [com.arjuna.ats.jta] (default task-18) TransactionSynchronizationRegistryImple.getTransactionKey

Happens on JBoss EAP 7.0.9.

I have this constellation in lots of places, but only here it breaks. Where can I look for additional clues?

In my code I narrowed it down to exactly the point before the method call and inside it.

[tomjenkinson]

Can it be reproduced on EAP 7.2.0?

[thomas.scheibelreiter]

Probably, since I found out that is intended behaviour. There is no transaction propagation with BMT, making it utterly useless.

[tomjenkinson]

I see, it is described in 8.6.1 of EJB 3.2