I have an entity that has a CallBackListener registered using postPersist and postUpdate. The listener takes the entity and submits the ID to a JMS queue which perform further processing. The message submission and consumption are so fast that they're occurring before the original session has completed it's transaction.

As a result the MDB either can't find the entity or the entity is stale. What I really want is a way to have the MDB check to verify that the original transaction is complete before consuming the message.

It's been suggested to use the Interceptor.afterTransactionCompletion method. However, is this any different than the postUpdate lifecycle event?