anchor.diff:      parallel publishers for specific topic/queue). Message broker cluster (or in single node) keeps
       track of slots which constitutes for a large part of operating state before the cluster went down.
   	When first message broker node of the cluster starts up, it will read the database to recreate
  -    the internal state to previous state. 
  +    the internal state to previous state.
       -->
       <recovery>
           <!--
  
positive.code:         <!-- Thrift is used to maintain and sync slot (message groups) ranges between MB nodes. -->
          <thriftServerHost><%= @mb_thrift_server %></thriftServerHost>
          <thriftServerPort><%= @mb_thrift_port %></thriftServerPort>
          <!--Thrift server reconnect timeout. Value specified in SECONDS-->
          <thriftServerReconnectTimeout>5</thriftServerReconnectTimeout>
          <!-- Hazelcast reliable topics are used to share all notifications across the MB cluster (e.g. subscription
          changes), And this property defines the time-to-live for a notification since its creation. (in Seconds) -->
          <clusterNotificationTimeout>10</clusterNotificationTimeout>
      </coordination>
  
      <!-- You can enable/disable specific messaging transports in this section. By default all 
      transports are enabled. This section also allows you to customize the messaging flows used 
      within WSO2 MB. NOT performance related, but logic related. -->
      <transports>
          <amqp enabled="true">
  
negative.code:   ~  under the License.
    -->
  
  <!-- This is the root configuration file of WSO2 Message Broker (MB). Links to configurations of
  associated libraries are also specified here.
  
  [Note for developers] - If you intend to rename or modify a property name, remember to update
  relevant, org.wso2.andes.configuration.enums.AndesConfiguration, enum value using the Xpath
  expression of the property.
  
  This file is ciphertool compliant. Refer PRODUCT_HOME/repository/conf/security/cipher-text.properties for examples.-->
  <broker>
  
      <coordination>
          <!-- You can override the cluster node identifier of this MB node using the nodeID.
          If it is left as "default", the default node ID will be generated for it. (Using IP + UUID).
          The node ID of each member should ALWAYS be unique.-->
          <nodeID>default</nodeID>
  