Why does the ActiveMQ broker start twice upon every Fabric container restart?

Issue

• Upon every Fabric broker container restart the ActiveMQ broker gets started twice during the container start-up. Sometimes the broker gets stopped during the first start-up which may raise exceptions like
  org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped.