In a Java EE server MDBs are executed with configurable transaction
semantics. By default, container-managed transaction semantics are used
which incorporate the consumption of the message by the MDB into a JTA
(which is XA) transaction which includes all other enlisted resources (e.g.
databases, J
Is this a race condition (i.e. the database transaction is committed if you
wait a second or two), or is the transaction ultimately failing and being
rolled back? If it's not the former, fix that problem (whatever it is)
first.
Tim
On Sat, Jul 31, 2021, 2:25 AM Ben Pirt wrote:
> We're modernisi
