Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-2484

JBM HeuristicMixedException may destabilise the resource used during transactional contexts

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.4 CP2
    • Fix Version/s: 4.4 CP3
    • Component/s: Transports
    • Labels:
      None

      Description

      JBoss Messaging sometimes causes a HeuristicMixedException to be raised by the transaction manager during commit. Once this happens the associated session would appear to be destabilised in that subsequent use does not appear possible

      The log files contain the following output.

      On the client side
      2009-03-03 07:17:13,137 118839811 ERROR [org.hibernate.transaction.JTATransaction] (JbpmJobExector:<ip addr>:12 JTA commit failed
      javax.transaction.HeuristicMixedException
      at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1414)
      at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
      at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
      at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
      at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:146)
      at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:295)
      at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:253

      This exception is sometimes, although not always, paired up with the following exception on the server side.

      2009-03-03 07:29:32,752 119400749 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkerThread#7[<ip addr>:35552] ConnectionEndpoint[2gw-biv0otrf-1-png68srf-w3rpob-v2p1hs4] sendTransaction [4bz-4vj97urf-1-png68srf-w3rpob-v2p1hs4]
      javax.jms.IllegalStateException: Cannot find session with id i2y-gk8bttrf-1-png68srf-w3rpob-v2p1hs4
      at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835)
      at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:497)
      at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
      at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
      at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195)
      at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source)

      The exceptions are always generated with the same session id which would suggest that there is an underlying issue in the JBoss Messaging codebase.

      We need to handle this until the issue is resolved within JBM.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kconner Kevin Conner
                  Reporter:
                  kconner Kevin Conner
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: