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
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.x
- 6.x
- HornetQ in XA scope
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
