[JCA/JBoss] - HeuristicMixedException: cause and remedy?
by kennardconsulting
Hi guys,
The JBoss Messaging guys suggested I post here (original thread here http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241134#4241134).
I'm having a hard time finding good documentation on javax.transaction.HeuristicMixedException. JBoss Messaging (and the old JBoss MQ) seems to throw this exception intermittently while processing large volumes of messages in a batch (say, 2000 messages over 3 cluster nodes):
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 worst thing is, once the exception is thrown, that node is effectively dead. No more JMS 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 message is sent to them.
Can anybody suggest why this error happens, and whether there is some setting to automatically recover from it? If I manually restart the node it works fine.
Regards,
Richard
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241309#4241309
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241309
16 years, 9 months
[JBoss Messaging] - Clusted FailOver doesn't seem to work correctly with Bridge
by artp
I have a cluster that I'll call cluster A that has a Bridge that moves messages from a Cluster A queue to another cluster's(Cluster B) queue. Cluster B contains two nodes(B0,B1). Initially, when i start all the nodes up all is well, messages are moved from Cluster A to one node(ie B0) in Cluster B.
When i take down B0, i get failover messages, on B1, saying that fail over is happening and it's completed. Natually, i'd expect further messages from Cluster A to be processed by B1. Sometimes FailOver works to B1, but most of the time it doesn't. When it doesn't I see the MessageCount and DeliveryCount grow higher has i send more messages from Cluster A. It looks as if the Bridge is doing it's job since i can see the messagecount from the jmx console. FailOver appears to be causing something to go wrong once messages get to B1. From that point on messages are stuck on B1.
To get the messages out of the stuck state i have to bring nodes up and down(ie. bring B0 up then take down B1). Eventually, the FailOver kicks in and one Node proceses the messages. Once that happens, messages are processed.
Is there something i'm missing?
Environment:
jboss 5.1, JBM 1.4.4 src, I modified JMSRemoteConnection to compile against Remoting 2.5.1, so we could have the Bridge fixes, etc.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241305#4241305
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241305
16 years, 9 months
[JBoss Tools (users)] - Re: High CPU on JSF auto-complete
by jboden
Thanks Max for your help,
I took your idea and stated a new project with one bean and one JSF page. As expected, it worked quickly. I then copied my 25 beans and 25 jsf pages, and added faces-config.xml entries. It then went back to 100% cpu.
Not sure if that's a valid test with all of the compile error present from just dropping in class files without the spring configs and related classes.
As far as screen shot, I simply hit Ctrl-Space and everything freezes.
At this point I think I'll have to punt and assume it's something in my project. If anyone has thoughts on what might do that, I appreciate your thoughts. Too many public methods, public or static vars in the beans? Anything Spring-related?
I'm including persistence beans into my faces beans as properties in faces-config.xml. <property-name> and . The one JSF bean that does respond quickly does not have these references, but it's also newly created. Not sure if that would matter or not.
Any thoughts would be great and we'll just live with it until future releases or faster hardware. :-)
Thanks!
It sounds like it's specific to my project.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241299#4241299
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241299
16 years, 9 months