JMS messages hang on remote server in XA transaction after "high CPU"
Issue
- A server which is consuming messages from remote server in XA transaction (using for example MDBs or EJBs) get impacted by "high CPU"
- this server stops responding for the duration of the impact so that messages can get starve in remote destination and even stay in this state if load returns to normal.
Environment
- JBoss Enterprise Application Platform [EAP] 6
- HornetQ in XA scope with remote JMS
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.