Issue

I'm in the process of setting up a new A-MQ dev platform within a Fabric environment. I currently have one master/slave pair that is working correctly. I have recently implemented the use of gateway-mq. I'm noticing that when I stop either the master or slave and leave it down the gateway no longer works, seems like both master & slave must be running. I'm wondering if I have a configuration issue or if there is something else going on. I'm using the gateway-mq profile within my broker group profile along with gateway properties file io.fabric8.gateway.detecting.properties that I have customized.

JBossA-MQ:admin@rootdevl09733jb601> container-list
[id] [version] [type] [connected] [profiles] [provision status]
rootdevl09733jb601* 1.1 karaf yes fabric success
fabric-ensemble-0000-1
esesb-esbint-amq1 1.1 karaf yes mq-broker-esesb-esbint-grp.esesb-esbint-amqdst success
esesb-esbint-amq2 1.1 karaf yes mq-broker-esesb-esbint-grp.esesb-esbint-amqdst success

Broker Profile:
mq-broker-esesb-esbint-grp.esesb-esbint-amqdst

Parents:
mq-base
gateway-mq

io.fabric8.gateway.detecting.properties:
port=8001
httpEnabled=true
openWireEnabled=true
stompEnabled=true
mqttEnabled=true
amqpEnabled=true
sslEnabled=false

defaultVirtualHost=esesb-esbint-grp
zooKeeperPath=/fabric/registry/clusters/amq

loadBalancerType=roundrobin
stickyLoadBalancerCacheSize=10000

io.fabric8.mq.fabric.server-esesb-esbint-amqdst.properties:

replicas = 2
standby.pool = default
broker-name = esesb-esbint-amqdst
keystore.password = tDde2okx
data = ${runtime.data}esesb-esbint-amqdst
keystore.file = profile:keystore.jks
ssl = true
kind = MasterSlave
truststore.file = profile:truststore.jks
keystore.cn = esesb-esbint-grp
connectors = openwire mqtt amqp stomp
truststore.password = tDde2okx
keystore.url = profile:keystore.jks
config = profile:ssl-broker.xml
group = esesb-esbint-grp