Why the Standalone Broker is shut down when Fabric is shut down or unaccessible ?
Issue
-
I created a standalone MQ broker using JBoss Fuse Management Console, it works but if root container is shut down or not accessible, broker shuts itself down. Is it possible for broker to not depend on root container?
-
Following kind of message appears in the
"karaf.log"file:
INFO | pool-10-thread-1 | ActiveMQServiceFactory | q.fabric.ActiveMQServiceFactory$ 64 | 116 - org.jboss.amq.mq-fabric - 6.1.0.redhat-379 | Lost zookeeper service for broker b2, stopping the broker.
- Broker configuration file as seen from the FMC is as following:
standby.pool = default
connectors = openwire
broker-name = b2
data = ${karaf.base}/data/b2
config = profile:broker.xml
group = b2
kind = StandAlone
network =
Environment
- Red Hat JBoss Fuse
- 6.1.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
