Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15609

There is no cleanup of thread bound transaction timeout override on threads used to run servlets

XMLWordPrintable

    • Hide

      See the README.md in the attached testcase.zip.

      Show
      See the README.md in the attached testcase.zip .
    • Hide

      A WebFilter can be used to clear the timeout override at the end of a servlet execution.

      Show
      A WebFilter can be used to clear the timeout override at the end of a servlet execution.

      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.

        1. testcase.zip
          9 kB

            [WFLY-15609] There is no cleanup of thread bound transaction timeout override on threads used to run servlets

            Lin Gao added a comment -

            Resolving it as duplicated, I cannot reproduce it in WildFly main branch.

            Lin Gao added a comment - Resolving it as duplicated, I cannot reproduce it in WildFly main branch.

            Lin Gao added a comment -

            I believe this is duplicated with WFLY-16514, and it has been fixed in both wildfly main branch and EAP8 beta: JBEAP-24037

            Lin Gao added a comment - I believe this is duplicated with  WFLY-16514 , and it has been fixed in both wildfly main branch and EAP8 beta: JBEAP-24037

            Cheng Fang added a comment -

            Since this affects servlet processing, it's best to be handled as part of servlet request processing.

            Cheng Fang added a comment - Since this affects servlet processing, it's best to be handled as part of servlet request processing.

            Michael Musgrove added a comment - - edited

            cfang@redhat.com the transaction state is maintained as a thread local in WFTC code [1] rather than narayana code so I reassigned the issue. I have done the same for the cloned JBEAP issue.

             

            [1]https://github.com/wildfly/wildfly-transaction-client/blob/master/src/main/java/org/wildfly/transaction/client/ContextTransactionManager.java#L48

            Michael Musgrove added a comment - - edited cfang@redhat.com the transaction state is maintained as a thread local in WFTC code [1]  rather than narayana code so I reassigned the issue. I have done the same for the cloned JBEAP issue.   [1] https://github.com/wildfly/wildfly-transaction-client/blob/master/src/main/java/org/wildfly/transaction/client/ContextTransactionManager.java#L48

              rhn-engineering-lgao Lin Gao
              rhn-support-sfikes Stephen Fikes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: