[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1706) JBoss Messaging sometimes causes a HeuristicMixedException

[Tim Fox (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12479696#action_12479696 ] 

Tim Fox commented on JBMESSAGING-1706:
--------------------------------------

>From what I have seen of this JBoss Messaging *does not* throw a HeuristicMixedException.

Let's look at the stack trace again:

javax.transaction.HeuristicMixedException
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate
(TransactionImple.java:1431)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction
.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDeleg
ate.java:75)
        at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.e
nd(JmsServerSession.java:657)
        at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:243)
        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)


The exception is being thrown from com.arjuna classes. (Arjuna is the old name for what is now known as JBoss Transactions).

The classes that begin with org.jboss.resource are classes in the JCA component of the JBoss Application Server.

The org.jboss.util classes are utility classes of the JBoss Application Server.

The rest of the classes are standard JDK classes.

I do not see even one JBoss Messaging class involved in this entire stack, so I don't really understand why you think this is a JBoss Messaging issue, or what we could do about it anyway since not one of the classes involved is from the JBoss Messaging project.

As I posted on the forums, more than likely the JCA adapter is doing something silly in starting/stopping/enlisting transactions and JBoss Transactions is (correctly) barfing.




> JBoss Messaging sometimes causes a HeuristicMixedException
> ----------------------------------------------------------
>
>                 Key: JBMESSAGING-1706
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1706
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.4.GA
>            Reporter: Richard Kennard
>            Assignee: Tim Fox
>
> I am raising this JIRA to ask the JBoss Messaging Team to take ownership of this issue.
> The issue is that JBM intermittently (ie. when processing large amounts of messages, when bringing up/shutting down nodes in a cluster) throws a HeuristicMixedException. Once it does, that node in the cluster is effectively dead. No more messages get processed. My app has multiple queues, but once one queue on the node fails (say, the e-mail queue) then all queues stop working (say, the reports queues): they all report HeuristicMixedException whenever a messages is sent to them.
> I am using a workaround by having a separate monitoring program that reboots the node whenever it gets stuck in this HeuristicMixedException state.
> The JBoss ESB team have also had to implement a workaround: https://jira.jboss.org/jira/browse/JBESB-2484
> Others on the forum are seeing this too: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241134#4241134
> According to Kevin Conner of the ESB team, Howard worked with them on a workaround: https://jira.jboss.org/jira/browse/JBPAPP-1642, but the issue persists.

-- 
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