-
Bug
-
Resolution: Done
-
Major
-
7.2.9.GA, 7.3.10.GA, 7.4.2.GA
There is no cleanup of thread bound transaction timeout override on threads used to run servlets. Consequently, depending on previous activity and the thread used to run a given servlet operation, timeout overrides from earlier activity may be unexpectedly applied. This differs from other scenarios such as BMT entities where an interceptor explicitly clears the thread at the end of a request.
- clones
-
WFLY-15609 There is no cleanup of thread bound transaction timeout override on threads used to run servlets
- Resolved
-
JBEAP-24037 Explicit transaction-timeout of a previous transaction from the same thread used instead of default transaction-timeout
- Closed
-
WFLY-16514 Explicit transaction-timeout of a previous transaction from the same thread used instead of default transaction-timeout
- Closed
- is cloned by
-
JBEAP-25237 [GSS](8.0.z) WFLY-15609 - There is no cleanup of thread bound transaction timeout override on threads used to run servlets
- Closed
- links to