A-MQ C++ client using CMS: consumer stalls if there is a failover during a transacted batch
Issue
A C/C++ application uses the Apache CMS library to consume from a master-slave A-MQ broker cluster. Messages are consumed in transacted batches. If a master broker fails during the consumption of a transacted batch then, although the CMS client reconnects to the new master broker, the consumer may be broken -- no further messages are consumed.
Environment
- JBoss A-MQ
- 6.1
- 6.2
- Apache CMS library
- 3.8.x or earlier
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.