Transaction timeout override reset on threads when CMT transactions run in JBoss EAP 7

Solution Verified - Updated -

Issue

  • Setting a transaction timeout override (e.g. using UserTransaction.setTransactionTimeout(int)) on a thread.
  • After a Container Managed Transaction (CMT) method completes the override has been reverted to the default transaction timeout.
    • The reversion occurs whether the CMT method starts a new transaction or uses an existing transaction context.
  • A subsequent transaction (BMT or CMT context) on the thread will run with the default transaction timeout.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content