Message Driven Bean (MDB) fails to re-establish connection to ActiveMQ broker using XA transactions

Solution In Progress - Updated -


MDBs in an XA environment on JBoss EAP, using a cluster of ActiveMQ servers, appear to lose connectivity to the broker. No messages are processed - the MDB appears "stale" and do not recover without a system restart.


This issue has been observed in systems with the following configurations:
- XA transactions are being used
- priorityBackup is true, or priorityURIs have been specified in the ActiveMQ connection URI
- EAP is able to connect to multiple, independent master/slave broker groups
- JTA connections are being provided by the ActiveMQ JCA Resource Adapter (RAR)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content