Narayana's implementation of @Transactional has special handling for async return types (e.g. CompletionStage). When the transactional method completes and returns an async type, Narayana suspends the transaction rather than ending it. Later, when the async object is completed, Narayana resumes the transaction while handling any callbacks.

This behavior was added as part of WFLY-13505 and JBTM-3246. The latter issue implies this behavior was only supposed to be used by MicroProfile applications. If so, then there is a bug, because the behavior also occurs even if MP does not exist.

I have an application where this behavior is undesirable; it causes other resources associated with the transaction to be released much later than they should be. Therefore, I would like to have some way to disable this behavior. I would be okay with disabling it at any level - the whole server, or per-deployment, or per-method.