Transaction timeout override not cleared at end of request on thread used to run a servlet in JBoss EAP

Solution Verified - Updated -


  • After a transaction timeout override is set (e.g. using UserTransaction.setTransactionTimeout(int)) during execution of a servlet, the timeout override remains bound on the thread.
  • Subsequent servlets run on the same thread will unexpectedly encounter the non-default transaction timeout override.


  • Red Hat JBoss Enterprise Application Platform EAP 7

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