Details
-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.1
-
None
-
None
Description
Doing a bit of messing around with fabric and the broker. So I create a fabric container with the mq-default profile applied to it. In hawtio I then go and edit the broker.xml file in mq-base, maybe change one of the memory limits or whatever. When I save the file I noticed that the broker wouldn't come up until I stopped and restarted the container a couple times. Checking the log of that fabric container I see that when I save the broker.xml the broker shuts down fine, but then when it comes back up it logs that it's waiting to become the master. Stopping and restarting the container clears this condition.