[esb-issues] [JBoss JIRA] Work started: (JBESB-2483) JBM HeuristicMixedException may destabilise the resource used during transactional contexts

[Kevin Conner (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JBESB-2483 started by Kevin Conner.

> JBM HeuristicMixedException may destabilise the resource used during transactional contexts
> -------------------------------------------------------------------------------------------
>
>                 Key: JBESB-2483
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2483
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>    Affects Versions: 4.5
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 4.6
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira