Fabric managed container tries to create two broker instances when adding the jboss-fuse-full Fabric profile.

Issue

When adding the jboss-fuse-full profile to a Fabric managed container that joined the Fabric via the fabric:join command, the embedded ActiveMQ broker fails to initialize on that container and raises this error:

java.io.IOException: Transport Connector could not be registered in JMX: 
java.io.IOException: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: 
java.net.BindException: Address already in use (Bind failed)

On closer inspection of the container log file there seem to be two broker instances of different names getting started:

Loading XML bean definitions from URL [file:etc/activemq.xml]
Loading XML bean definitions from URL [profile:broker.xml]

Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/rh/jboss-fuse-6.3.0.redhat-283/data/amq/kahadb]
Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/rh/jboss-fuse-6.3.0.redhat-283/data/root2/kahadb]