Rolled back JTA TX marked active/inflight

Question

          Hello. I am writing a message driven bean that utilizes container managed transaction
          demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          The MDB relays message information to a legacy system. If the legacy system is
          down, I want to retry message delivery at a later point, so I mark the current
          transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          This causes the EJB container to continually call onMessage() with my message
          beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          however, are marked as active/inflight by the WLS transaction manager, leading
          to resource starvation and inability to create transactions because of an overflow
          of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          although the JTA monitoring tools clearly indicate that the TX has been rolled
          back.
          Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          Please cc: me if you respond as well
          Thanks,
          Alex
          ---- snippets follow ----
          Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          page
          Name Status Servers Resources Properties
          (key=value)
          (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          alexd {JMS_jmsStoreTest=rolledback} (none)
          And a listing of the JTA monitoring info
          Total Transactions: 45060
          Total Committed: 131
          Total Rolled Back: 44929
          Timeout Rollbacks: 0
          Resource Rollbacks: 0
          Application Rollbacks: 44929
          

Answer 1

I know this is fixed in WLS 6.1's GA release. Basically, the problem is
          that the EJB container is marking the transaction for rollback where it
          should be rolling it back. That's why you have so many tx's in-flight.
          They are waiting to time-out.
          -- Rob
          Alex DeNeui wrote:
          >
          > Hello. I am writing a message driven bean that utilizes container managed transaction
          > demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          >
          > The MDB relays message information to a legacy system. If the legacy system is
          > down, I want to retry message delivery at a later point, so I mark the current
          > transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          > This causes the EJB container to continually call onMessage() with my message
          > beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          > however, are marked as active/inflight by the WLS transaction manager, leading
          > to resource starvation and inability to create transactions because of an overflow
          > of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          > although the JTA monitoring tools clearly indicate that the TX has been rolled
          > back.
          >
          > Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          > list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          >
          > Please cc: me if you respond as well
          >
          > Thanks,
          > Alex
          >
          > ---- snippets follow ----
          >
          > Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          > page
          > -----------------
          > Name Status Servers Resources Properties
          > (key=value)
          > (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          > alexd {JMS_jmsStoreTest=rolledback} (none)
          > -----------------
          >
          > And a listing of the JTA monitoring info
          > -----------------
          > Total Transactions: 45060
          > Total Committed: 131
          > Total Rolled Back: 44929
          > Timeout Rollbacks: 0
          > Resource Rollbacks: 0
          > Application Rollbacks: 44929
          > ------------------
          Coming Soon: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnweblogic.com