You need to add you slave to <connectors> on master (and master host to slave 
<connectors>). Command line doesn't do that automatically, it only creates 
initial configuration.

-- 
    Vilius

-----Original Message-----
From: Adrija Basu <adrija.tin...@gmail.com> 
Sent: Tuesday, November 21, 2023 7:19 AM
To: users@activemq.apache.org
Subject: Re: HA setup using shared store policy

Hello Team

Please find the error I am facing:

2023-11-21 10:45:41,583 INFO  [org.apache.activemq.artemis] AMQ241004:
Artemis Console available at http://localhost:8162/console
2023-11-21 10:45:50,424 WARN  [org.apache.activemq.artemis.core.server]
AMQ222137: Unable to announce backup, retrying
org.apache.activemq.artemis.api.core.ActiveMQConnectionTimedOutException:
AMQ219012: Timed out waiting to receive initial broadcast from cluster
        at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.executeDiscovery(ServerLocatorImpl.java:795)
~[artemis-core-client-2.31.0.jar:2.31.0]
        at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:676)
~[artemis-core-client-2.31.0.jar:2.31.0]
        at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:570)
~[artemis-core-client-2.31.0.jar:2.31.0]
        at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:549)
~[artemis-core-client-2.31.0.jar:2.31.0]
        at
org.apache.activemq.artemis.core.server.cluster.BackupManager$BackupConnector$1.run(BackupManager.java:273)
~[artemis-server-2.31.0.jar:2.31.0]
        at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:57)
~[artemis-commons-2.31.0.jar:?]
        at
org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:32)
~[artemis-commons-2.31.0.jar:?]
        at
org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:68)
~[artemis-commons-2.31.0.jar:?]

also please find the broker.xml for both master and slave:

Master:

<?xml version='1.0'?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more contributor 
license agreements.  See the NOTICE file distributed with this work for 
additional information regarding copyright ownership.  The ASF licenses this 
file to you under the Apache License, Version 2.0 (the "License"); you may not 
use this file except in compliance with the License.  You may obtain a copy of 
the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed 
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR 
CONDITIONS OF ANY KIND, either express or implied.  See the License for the 
specific language governing permissions and limitations under the License.
-->

<configuration xmlns="urn:activemq"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
               xmlns:xi="http://www.w3.org/2001/XInclude";
               xsi:schemaLocation="urn:activemq 
/schema/artemis-configuration.xsd">

   <core xmlns="urn:activemq:core" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
         xsi:schemaLocation="urn:activemq:core ">

      <name>0.localhost</name>


      <persistence-enabled>true</persistence-enabled>

      <!-- It is recommended to keep this value as 1, maximizing the number of 
records stored about redeliveries.
           However if you must preserve state of individual redeliveries, you 
may increase this value or set it to -1 (infinite). -->
      <max-redelivery-records>1</max-redelivery-records>

      <!-- this could be ASYNCIO, MAPPED, NIO
           ASYNCIO: Linux Libaio
           MAPPED: mmap files
           NIO: Plain Java Files
       -->
      <journal-type>ASYNCIO</journal-type>

      <paging-directory>data/paging</paging-directory>

      <bindings-directory>data/bindings</bindings-directory>

      <journal-directory>data/journal</journal-directory>


<large-messages-directory>data/large-messages</large-messages-directory>


      <!-- if you want to retain your journal uncomment this following 
configuration.

      This will allow your system to keep 7 days of your data, up to 10G.
Tweak it accordingly to your use case and capacity.

      it is recommended to use a separate storage unit from the journal for 
performance considerations.

      <journal-retention-directory period="7" unit="DAYS"
storage-limit="10G">data/retention</journal-retention-directory>

      You can also enable retention by using the argument journal-retention on 
the `artemis create` command -->



      <journal-datasync>true</journal-datasync>

      <journal-min-files>2</journal-min-files>

      <journal-pool-files>10</journal-pool-files>

      <journal-device-block-size>4096</journal-device-block-size>

      <journal-file-size>10M</journal-file-size>

      <!--
       This value was determined through a calculation.
       Your system could perform 17.86 writes per millisecond
       on the current journal configuration.
       That translates as a sync write every 56000 nanoseconds.

       Note: If you specify 0 the system will perform writes directly to the 
disk.
             We recommend this to be 0 if you are using journalType=MAPPED and 
journal-datasync=false.
      -->
      <journal-buffer-timeout>56000</journal-buffer-timeout>


      <!--
        When using ASYNCIO, this will determine the writing queue depth for 
libaio.
       -->
      <journal-max-io>4096</journal-max-io>
      <!--
        You can verify the network health of a particular NIC by specifying the 
<network-check-NIC> element.
         <network-check-NIC>theNicName</network-check-NIC>
        -->

      <!--
        Use this to use an HTTP server to validate the network
         <network-check-URL-list>http://www.apache.org</network-check-URL-list>
-->

      <!-- <network-check-period>10000</network-check-period> -->
      <!-- <network-check-timeout>1000</network-check-timeout> -->

      <!-- this is a comma separated list, no spaces, just DNS or IPs
           it should accept IPV6

           Warning: Make sure you understand your network topology as this is 
meant to validate if your network is valid.
                    Using IPs that could eventually disappear or be partially 
visible may defeat the purpose.
                    You can use a list of multiple IPs, and if any successful 
ping will make the server OK to continue running -->
      <!-- <network-check-list>10.0.0.1</network-check-list> -->

      <!-- use this to customize the ping used for ipv4 addresses -->
      <!-- <network-check-ping-command>ping -c 1 -t %d 
%s</network-check-ping-command> -->

      <!-- use this to customize the ping used for ipv6 addresses -->
      <!-- <network-check-ping6-command>ping6 -c 1 
%2$s</network-check-ping6-command> -->



    <connectors>
        <!-- Connector used to be announced through cluster connections and 
notifications -->
        <connector name="artemis">tcp://0.localhost:61616</connector>
    </connectors>



      <!-- how often we are looking for how many bytes are being used on the 
disk in ms -->
      <disk-scan-period>5000</disk-scan-period>

      <!-- once the disk hits this limit the system will block, or close the 
connection in certain protocols
           that won't support flow control. -->
      <max-disk-usage>90</max-disk-usage>

      <!-- should the broker detect dead locks and other issues -->
      <critical-analyzer>true</critical-analyzer>

      <critical-analyzer-timeout>120000</critical-analyzer-timeout>

      <critical-analyzer-check-period>60000</critical-analyzer-check-period>

      <critical-analyzer-policy>HALT</critical-analyzer-policy>


      <page-sync-timeout>1108000</page-sync-timeout>


      <!-- the system will enter into page mode once you hit this limit.
This is an estimate in bytes of how much the messages are using in memory

      The system will use half of the available memory (-Xmx) by default for 
the global-max-size.
      You may specify a different value here if you need to customize it to 
your needs.

      <global-max-size>100Mb</global-max-size> -->

      <!-- the maximum number of messages accepted before entering full address 
mode.
           if global-max-size is specified the full address mode will be 
specified by whatever hits it first. -->
      <global-max-messages>-1</global-max-messages>

      <acceptors>

         <!-- useEpoll means: it will use Netty epoll if you are on a system 
(Linux) that supports it -->
         <!-- amqpCredits: The number of credits sent to AMQP producers -->
         <!-- amqpLowCredits: The server will send the # credits specified at 
amqpCredits at this low mark -->
         <!-- amqpDuplicateDetection: If you are not using duplicate detection, 
set this to false
                                      as duplicate detection requires 
applicationProperties to be parsed on the server. -->
         <!-- amqpMinLargeMessageSize: Determines how many bytes are considered 
large, so we start using files to hold their data.
                                       default: 102400, -1 would mean to 
disable large message control -->

         <!-- Note: If an acceptor needs to be compatible with HornetQ and/or 
Artemis 1.x clients add
                    "anycastPrefix=jms.queue.;multicastPrefix=jms.topic."
to the acceptor url.
                    See https://issues.apache.org/jira/browse/ARTEMIS-1644
for more information. -->


         <!-- Acceptor for every supported protocol -->
         <acceptor
name="artemis">tcp://0.localhost:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false</acceptor>

         <!-- AMQP Acceptor.  Listens on default AMQP port for AMQP traffic.-->
         <acceptor
name="amqp">tcp://0.localhost:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true</acceptor>

         <!-- STOMP Acceptor. -->
         <acceptor
name="stomp">tcp://0.localhost:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>

         <!-- HornetQ Compatibility Acceptor.  Enables HornetQ Core and STOMP 
for legacy HornetQ clients. -->
         <acceptor
name="hornetq">tcp://0.localhost:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true</acceptor>

         <!-- MQTT Acceptor -->
         <acceptor
name="mqtt">tcp://0.localhost:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true</acceptor>

      </acceptors>


      <cluster-user>admin</cluster-user>

      <cluster-password>admin</cluster-password>

      <broadcast-groups>
         <broadcast-group name="bg-group1">
            <group-address>231.7.7.7</group-address>
            <group-port>9876</group-port>
            <broadcast-period>5000</broadcast-period>
            <connector-ref>artemis</connector-ref>
         </broadcast-group>
      </broadcast-groups>

      <discovery-groups>
         <discovery-group name="dg-group1">
            <group-address>231.7.7.7</group-address>
            <group-port>9876</group-port>
            <refresh-timeout>10000</refresh-timeout>
         </discovery-group>
      </discovery-groups>

      <cluster-connections>
         <cluster-connection name="my-cluster">
            <connector-ref>artemis</connector-ref>
            <message-load-balancing>ON_DEMAND</message-load-balancing>
            <max-hops>0</max-hops>
            <discovery-group-ref discovery-group-name="dg-group1"/>
         </cluster-connection>
      </cluster-connections>


      <ha-policy>
         <shared-store>
            <master>
               <failover-on-shutdown>true</failover-on-shutdown>
            </master>
         </shared-store>
      </ha-policy>

      <security-settings>
         <security-setting match="#">
            <permission type="createNonDurableQueue" roles="amq"/>
            <permission type="deleteNonDurableQueue" roles="amq"/>
            <permission type="createDurableQueue" roles="amq"/>
            <permission type="deleteDurableQueue" roles="amq"/>
            <permission type="createAddress" roles="amq"/>
            <permission type="deleteAddress" roles="amq"/>
            <permission type="consume" roles="amq"/>
            <permission type="browse" roles="amq"/>
            <permission type="send" roles="amq"/>
            <!-- we need this otherwise ./artemis data imp wouldn't work -->
            <permission type="manage" roles="amq"/>
         </security-setting>
      </security-settings>

      <address-settings>
         <!-- if you define auto-create on certain queues, management has to be 
auto-create -->
         <address-setting match="activemq.management#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>
            <!-- with -1 only the global-max-size is in use for limiting -->
            <max-size-bytes>-1</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
         </address-setting>
         <!--default for catch all-->
         <address-setting match="#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>


<message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
            <auto-delete-queues>false</auto-delete-queues>
            <auto-delete-addresses>false</auto-delete-addresses>

            <!-- The size of each page file -->
            <page-size-bytes>10M</page-size-bytes>

            <!-- When we start applying the address-full-policy, e.g paging
-->
            <!-- Both are disabled by default, which means we will use the 
global-max-size/global-max-messages  -->
            <max-size-bytes>-1</max-size-bytes>
            <max-size-messages>-1</max-size-messages>

            <!-- When we read from paging into queues (memory) -->

            <max-read-page-messages>-1</max-read-page-messages>
            <max-read-page-bytes>20M</max-read-page-bytes>

            <!-- Limit on paging capacity before starting to throw errors
-->

            <page-limit-bytes>-1</page-limit-bytes>
            <page-limit-messages>-1</page-limit-messages>
          </address-setting>
      </address-settings>

      <addresses>
         <address name="DLQ">
            <anycast>
               <queue name="DLQ" />
            </anycast>
         </address>
         <address name="ExpiryQueue">
            <anycast>
               <queue name="ExpiryQueue" />
            </anycast>
         </address>

      </addresses>


      <!-- Uncomment the following if you want to use the Standard 
LoggingActiveMQServerPlugin pluging to log in events
      <broker-plugins>
         <broker-plugin
class-name="org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin">
            <property key="LOG_ALL_EVENTS" value="true"/>
            <property key="LOG_CONNECTION_EVENTS" value="true"/>
            <property key="LOG_SESSION_EVENTS" value="true"/>
            <property key="LOG_CONSUMER_EVENTS" value="true"/>
            <property key="LOG_DELIVERING_EVENTS" value="true"/>
            <property key="LOG_SENDING_EVENTS" value="true"/>
            <property key="LOG_INTERNAL_EVENTS" value="true"/>
         </broker-plugin>
      </broker-plugins>
      -->

   </core>
</configuration>

Slave:

<?xml version='1.0'?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more contributor 
license agreements.  See the NOTICE file distributed with this work for 
additional information regarding copyright ownership.  The ASF licenses this 
file to you under the Apache License, Version 2.0 (the "License"); you may not 
use this file except in compliance with the License.  You may obtain a copy of 
the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed 
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR 
CONDITIONS OF ANY KIND, either express or implied.  See the License for the 
specific language governing permissions and limitations under the License.
-->

<configuration xmlns="urn:activemq"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
               xmlns:xi="http://www.w3.org/2001/XInclude";
               xsi:schemaLocation="urn:activemq 
/schema/artemis-configuration.xsd">

   <core xmlns="urn:activemq:core" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
         xsi:schemaLocation="urn:activemq:core ">

      <name>0.localhost</name>


      <persistence-enabled>true</persistence-enabled>

      <!-- It is recommended to keep this value as 1, maximizing the number of 
records stored about redeliveries.
           However if you must preserve state of individual redeliveries, you 
may increase this value or set it to -1 (infinite). -->
      <max-redelivery-records>1</max-redelivery-records>

      <!-- this could be ASYNCIO, MAPPED, NIO
           ASYNCIO: Linux Libaio
           MAPPED: mmap files
           NIO: Plain Java Files
       -->
      <journal-type>ASYNCIO</journal-type>

      <paging-directory>/data/paging</paging-directory>

      <bindings-directory>/data/bindings</bindings-directory>

      <journal-directory>/data/journal</journal-directory>


<large-messages-directory>/data/large-messages</large-messages-directory>


      <!-- if you want to retain your journal uncomment this following 
configuration.

      This will allow your system to keep 7 days of your data, up to 10G.
Tweak it accordingly to your use case and capacity.

      it is recommended to use a separate storage unit from the journal for 
performance considerations.

      <journal-retention-directory period="7" unit="DAYS"
storage-limit="10G">data/retention</journal-retention-directory>

      You can also enable retention by using the argument journal-retention on 
the `artemis create` command -->



      <journal-datasync>true</journal-datasync>

      <journal-min-files>2</journal-min-files>

      <journal-pool-files>10</journal-pool-files>

      <journal-device-block-size>4096</journal-device-block-size>

      <journal-file-size>10M</journal-file-size>

      <!--
       This value was determined through a calculation.
       Your system could perform 17.86 writes per millisecond
       on the current journal configuration.
       That translates as a sync write every 56000 nanoseconds.

       Note: If you specify 0 the system will perform writes directly to the 
disk.
             We recommend this to be 0 if you are using journalType=MAPPED and 
journal-datasync=false.
      -->
      <journal-buffer-timeout>56000</journal-buffer-timeout>


      <!--
        When using ASYNCIO, this will determine the writing queue depth for 
libaio.
       -->
      <journal-max-io>4096</journal-max-io>
      <!--
        You can verify the network health of a particular NIC by specifying the 
<network-check-NIC> element.
         <network-check-NIC>theNicName</network-check-NIC>
        -->

      <!--
        Use this to use an HTTP server to validate the network
         <network-check-URL-list>http://www.apache.org</network-check-URL-list>
-->

      <!-- <network-check-period>10000</network-check-period> -->
      <!-- <network-check-timeout>1000</network-check-timeout> -->

      <!-- this is a comma separated list, no spaces, just DNS or IPs
           it should accept IPV6

           Warning: Make sure you understand your network topology as this is 
meant to validate if your network is valid.
                    Using IPs that could eventually disappear or be partially 
visible may defeat the purpose.
                    You can use a list of multiple IPs, and if any successful 
ping will make the server OK to continue running -->
      <!-- <network-check-list>10.0.0.1</network-check-list> -->

      <!-- use this to customize the ping used for ipv4 addresses -->
      <!-- <network-check-ping-command>ping -c 1 -t %d 
%s</network-check-ping-command> -->

      <!-- use this to customize the ping used for ipv6 addresses -->
      <!-- <network-check-ping6-command>ping6 -c 1 
%2$s</network-check-ping6-command> -->



    <connectors>
        <!-- Connector used to be announced through cluster connections and 
notifications -->
        <connector name="artemis">tcp://localhost:61616</connector>
    </connectors>



      <!-- how often we are looking for how many bytes are being used on the 
disk in ms -->
      <disk-scan-period>5000</disk-scan-period>

      <!-- once the disk hits this limit the system will block, or close the 
connection in certain protocols
           that won't support flow control. -->
      <max-disk-usage>90</max-disk-usage>

      <!-- should the broker detect dead locks and other issues -->
      <critical-analyzer>true</critical-analyzer>

      <critical-analyzer-timeout>120000</critical-analyzer-timeout>

      <critical-analyzer-check-period>60000</critical-analyzer-check-period>

      <critical-analyzer-policy>HALT</critical-analyzer-policy>


      <page-sync-timeout>1116000</page-sync-timeout>


      <!-- the system will enter into page mode once you hit this limit.
This is an estimate in bytes of how much the messages are using in memory

      The system will use half of the available memory (-Xmx) by default for 
the global-max-size.
      You may specify a different value here if you need to customize it to 
your needs.

      <global-max-size>100Mb</global-max-size> -->

      <!-- the maximum number of messages accepted before entering full address 
mode.
           if global-max-size is specified the full address mode will be 
specified by whatever hits it first. -->
      <global-max-messages>-1</global-max-messages>

      <acceptors>

         <!-- useEpoll means: it will use Netty epoll if you are on a system 
(Linux) that supports it -->
         <!-- amqpCredits: The number of credits sent to AMQP producers -->
         <!-- amqpLowCredits: The server will send the # credits specified at 
amqpCredits at this low mark -->
         <!-- amqpDuplicateDetection: If you are not using duplicate detection, 
set this to false
                                      as duplicate detection requires 
applicationProperties to be parsed on the server. -->
         <!-- amqpMinLargeMessageSize: Determines how many bytes are considered 
large, so we start using files to hold their data.
                                       default: 102400, -1 would mean to 
disable large message control -->

         <!-- Note: If an acceptor needs to be compatible with HornetQ and/or 
Artemis 1.x clients add
                    "anycastPrefix=jms.queue.;multicastPrefix=jms.topic."
to the acceptor url.
                    See https://issues.apache.org/jira/browse/ARTEMIS-1644
for more information. -->


         <!-- Acceptor for every supported protocol -->
         <acceptor
name="artemis">tcp://localhost:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=false;suppressInternalManagementObjects=false</acceptor>

         <!-- AMQP Acceptor.  Listens on default AMQP port for AMQP traffic.-->
         <acceptor
name="amqp">tcp://localhost:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true</acceptor>

         <!-- STOMP Acceptor. -->
         <acceptor
name="stomp">tcp://localhost:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true</acceptor>

         <!-- HornetQ Compatibility Acceptor.  Enables HornetQ Core and STOMP 
for legacy HornetQ clients. -->
         <acceptor
name="hornetq">tcp://localhost:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true</acceptor>

         <!-- MQTT Acceptor -->
         <acceptor
name="mqtt">tcp://localhost:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true</acceptor>

      </acceptors>


      <cluster-user>admin</cluster-user>

      <cluster-password>admin</cluster-password>

      <broadcast-groups>
         <broadcast-group name="bg-group1">
            <group-address>231.7.7.7</group-address>
            <group-port>9876</group-port>
            <broadcast-period>5000</broadcast-period>
            <connector-ref>artemis</connector-ref>
         </broadcast-group>
      </broadcast-groups>

      <discovery-groups>
         <discovery-group name="dg-group1">
            <group-address>231.7.7.7</group-address>
            <group-port>9876</group-port>
            <refresh-timeout>10000</refresh-timeout>
         </discovery-group>
      </discovery-groups>

      <cluster-connections>
         <cluster-connection name="my-cluster">
            <connector-ref>artemis</connector-ref>
            <message-load-balancing>ON_DEMAND</message-load-balancing>
            <max-hops>0</max-hops>
            <discovery-group-ref discovery-group-name="dg-group1"/>
         </cluster-connection>
      </cluster-connections>


      <ha-policy>
         <shared-store>
            <slave>
               <allow-failback>true</allow-failback>
            </slave>
         </shared-store>
      </ha-policy>

      <security-settings>
         <security-setting match="#">
            <permission type="createNonDurableQueue" roles="amq"/>
            <permission type="deleteNonDurableQueue" roles="amq"/>
            <permission type="createDurableQueue" roles="amq"/>
            <permission type="deleteDurableQueue" roles="amq"/>
            <permission type="createAddress" roles="amq"/>
            <permission type="deleteAddress" roles="amq"/>
            <permission type="consume" roles="amq"/>
            <permission type="browse" roles="amq"/>
            <permission type="send" roles="amq"/>
            <!-- we need this otherwise ./artemis data imp wouldn't work -->
            <permission type="manage" roles="amq"/>
         </security-setting>
      </security-settings>

      <address-settings>
         <!-- if you define auto-create on certain queues, management has to be 
auto-create -->
         <address-setting match="activemq.management#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>
            <!-- with -1 only the global-max-size is in use for limiting -->
            <max-size-bytes>-1</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
         </address-setting>
         <!--default for catch all-->
         <address-setting match="#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>


<message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
            <auto-delete-queues>false</auto-delete-queues>
            <auto-delete-addresses>false</auto-delete-addresses>

            <!-- The size of each page file -->
            <page-size-bytes>10M</page-size-bytes>

            <!-- When we start applying the address-full-policy, e.g paging
-->
            <!-- Both are disabled by default, which means we will use the 
global-max-size/global-max-messages  -->
            <max-size-bytes>-1</max-size-bytes>
            <max-size-messages>-1</max-size-messages>

            <!-- When we read from paging into queues (memory) -->

            <max-read-page-messages>-1</max-read-page-messages>
            <max-read-page-bytes>20M</max-read-page-bytes>

            <!-- Limit on paging capacity before starting to throw errors
-->

            <page-limit-bytes>-1</page-limit-bytes>
            <page-limit-messages>-1</page-limit-messages>
          </address-setting>
      </address-settings>

      <addresses>
         <address name="DLQ">
            <anycast>
               <queue name="DLQ" />
            </anycast>
         </address>
         <address name="ExpiryQueue">
            <anycast>
               <queue name="ExpiryQueue" />
            </anycast>
         </address>

      </addresses>


      <!-- Uncomment the following if you want to use the Standard 
LoggingActiveMQServerPlugin pluging to log in events
      <broker-plugins>
         <broker-plugin
class-name="org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin">
            <property key="LOG_ALL_EVENTS" value="true"/>
            <property key="LOG_CONNECTION_EVENTS" value="true"/>
            <property key="LOG_SESSION_EVENTS" value="true"/>
            <property key="LOG_CONSUMER_EVENTS" value="true"/>
            <property key="LOG_DELIVERING_EVENTS" value="true"/>
            <property key="LOG_SENDING_EVENTS" value="true"/>
            <property key="LOG_INTERNAL_EVENTS" value="true"/>
         </broker-plugin>
      </broker-plugins>
      -->

   </core>
</configuration>


Thanks And Regards
Adrija

On Mon, Nov 20, 2023 at 10:11 PM Domenico Francesco Bruscino < 
bruscin...@gmail.com> wrote:

> Hi Adrija,
>
> this mailing list doesn't support attachments so your files and 
> screenshot didn't come through. Please cut and paste the error logs instead.
>
> Regards,
> Domenico
>
> On Mon, 20 Nov 2023 at 16:37, Adrija Basu <adrija.tin...@gmail.com> wrote:
>
> > Hello Team
> >
> > Can you please assist on the below query
> >
> > Thanks And Regards
> > Adrija
> >
> > On Mon, 20 Nov, 2023, 19:45 Adrija Basu, <adrija.tin...@gmail.com>
> wrote:
> >
> >> Hello Team
> >>
> >> I am trying to setup HA and failover using shared store policy on
> centos7
> >> local vm for that I created the master and slave broker using the
> following
> >> commands from the path :
> >> /opt/artemis/bin
> >>
> >> ./artemis create shstoremaster1 --clustered --shared-store
> --default-port
> >> 61616 --http-port 8161 --user admin --password admin --host 
> >> localhost --cluster-user admin --cluster-password admin 
> >> --allow-anonymous --allow-anonymous  for master
> >>
> >> and
> >>
> >> ./artemis create --slave shstorslave --clustered --shared-store 
> >> --default-port 61616 --http-port 8162 --user admin --password admin
> --host
> >> localhost --cluster-user admin --cluster-password admin
> --allow-anonymous
> >> --allow-anonymous
> >>
> >> I have modified broker.xml ,bootstrap.xml and jolokia.xml files for 
> >> both master and slave ,I am attaching all the 6 files here
> >>
> >>
> >> Please note I am extremly new to active m artemis and just learning
> these
> >> concepts I know I am doing some mistakes in any of the 6 files but
> unable
> >> to figure it out so if you can help me to help me to figure out 
> >> what is
> the
> >> isue and how can I resolve it it will be very helpful for me also 
> >> please note for the master I am able to access it over port 8161 
> >> but for
> backup on
> >> port 8162I am getting the error as :
> >>
> >> [image: image.png]
> >> Please note I have tried changing localhost to 0.0.0.0 in all the 3
> files
> >> for slave but with no luck I have went through the dcumentation 
> >> from
> >>
> https://activemq.apache.org/components/artemis/documentation/latest/ha
> .html#high-availability-and-failover
> >> thoroughly but couldnt get anything ,your quick response is highly 
> >> acceptable Thanks and Regards *Adrija Basu*
> >>
> >
>


--
*Adrija Basu*

Reply via email to