How to mitigate risk of duplicate messages on XA scenarios under impact?
Issue
- When JBoss Enterprise Application Platform (EAP) 6 is under external impact, like "high CPU" caused by another process and the application uses JMS in a XA scenario; Transactions can end in a heuristic state and/or messages get duplicated .
Environment
- JBoss Enterprise Application Platform (EAP) 6
- HornetQ in XA scope
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
