Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.16.4
-
None
-
None
Description
A user has reported (with an example) that setting a transaction timeout on the UserTransaction will leak the timeout onto the thread and subsequent transaction creation on that thread uses the leaked value instead of new values. The com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction is using a ThreadLocal (_timeouts) for tracking timeouts but it is never cleared/reset.
More details in the referenced forum thread.