[
https://jira.jboss.org/browse/JBMESSAGING-1706?page=com.atlassian.jira.pl...
]
Piyush Panda commented on JBMESSAGING-1706:
-------------------------------------------
Hi Howard,
Thanks for the quick response. In my case the JMS Service and the java client are on the
same physical machine, so I am not able to understand why the network failure is
occurring. I have attached the JBOSS server logs and the client logs. Please have a look
at them. Any further inputs will be highly appreciable.
Also would adding a retry logic on MessagingJMSException in this case be a correct
decision?
Thanks,
Piyush
JBoss Messaging sometimes causes a HeuristicMixedException
----------------------------------------------------------
Key: JBMESSAGING-1706
URL:
https://jira.jboss.org/browse/JBMESSAGING-1706
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.4.GA
Reporter: Richard Kennard
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA
Attachments: Client_Logs.txt, JBOSS_Server_Logs.txt, server.zip
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#...
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/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira