Why does the ActiveMQ broker start twice upon every Fabric container restart?
Issue
- Upon every Fabric broker container restart the ActiveMQ broker gets started twice during the container start-up. Sometimes the broker gets stopped during the first start-up which may raise exceptions like
org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped.
Environment
- Fuse 6.x
- Fabric mode
- Fabric managed AMQ broker
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.