In fabric environment changes to broker.xml are not being picked up for mq group.
Issue
- User need to customize the broker.xml for a specific mq group, after editing the profile and recycling the containers the changes are not being picked up.
JBossA-MQ:admin@root> container-list
[id] [version] [type] [connected] [profiles] [provision status]
root* 1.0 karaf yes fabric success
fabric-ensemble-0000-1
ams-eisdev-amq1 1.0 karaf yes default success
mq-broker-mq-broker-ams-grp.ams-eisdev-profile
ams-eisdev-amq2 1.0 karaf yes default success
mq-broker-mq-broker-ams-grp.ams-eisdev-profile
fabric:profile-edit --resource broker.xml mq-broker-mq-broker-ams-grp.ams-eisdev-profile
- User cut and pasted the contents of the
broker.xmlfrom profilemq-baseinto new profile and customized the transport connector ports as seen here.
<transportConnectors>
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>
<!--transportConnector name="mqtt" uri="mqtt://0.0.0.0:0"/-->
<!--transportConnector name="amqp" uri="amqp://0.0.0.0:0"/-->
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
<transportConnector name="ws" uri="ws://0.0.0.0:61614"/>
</transportConnectors>
- After recycling the containers user doesn't see any of the above ports when displaying with
cluster-list.
ams-eisdev-profile ams-eisdev-amq1 ams-eisdev-amq2 tcp://hostname:39409, mqtt://hostname:51432, amqp://hostname:38717, stomp://hostname:47811
apis/rest/FabricResource/fabric8/1.0
Environment
- Red Hat JBoss A-MQ
- 6.2.0
- Red Hat JBoss Fuse
- 6.2.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.
