Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4481

Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread

    XMLWordPrintable

Details

    Description

      If a transaction timeout occurs, the UserTransaction object does not get cleaned up from the thread, even after the request ends and the thread returns to the pool. Future requests will not be able to begin() a transaction, since the STATUS_ROLLEDBACK UserTransaction throws this exception:

      Caused by: javax.transaction.NotSupportedException
      at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:79)
      at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:77)
      at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:124)
      at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:29)

      This means that any transaction timeout that occurs will leave the application server in a permanently broken state and require a server restart. Hence 4.2.0.GA is currently unusable in production!

      This needs to be fixed in an immediate patch release.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-217 JBAS-4481: Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-227 Thread-to-transaction association not changing for application threads on rollback for timed out transactions

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBAS-3633 Tidyup logging when transaction is no longer active

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              adrian.brock Adrian Brock (Inactive)
              gavin.king Gavin King (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: