Transaction timeout override not cleared at end of request on thread used to run a servlet in JBoss EAP
Issue
- 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.
Environment
- 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.