Migrate Standalone HornetQ Configuration to ActiveMQ Cluster

<queue name="feederInQueue">
    <entry name="/queue/feederInQueue"/>
</queue>

<topic name="feederOutTopic">
    <entry name="/topic/feederOutTopic"/>
</topic>

<addresses>
  <address name="feederInQueue">
    <anycast>
      <queue name="/queue/feederInQueue"/>
    </anycast>
  </address>
  <address name="/topic/feederOutTopic">
  </address>
<addresses>

<security-settings>
<security-setting match="#">
<permission type="createNonDurableQueue" roles="guest" />
<permission type="deleteNonDurableQueue" roles="guest" />
          <permission type="createDurableQueue" roles="guest" />
<permission type="deleteDurableQueue" roles="guest" />
<permission type="consume" roles="guest" />
<permission type="send" roles="guest" />
</security-setting>
</security-settings>

<security-setting match="globalqueues.europe.#">
   <permission type="createDurableQueue" roles="admin"/>
   <permission type="deleteDurableQueue" roles="admin"/>
   <permission type="createNonDurableQueue" roles="admin, guest, europe-users"/>
   <permission type="deleteNonDurableQueue" roles="admin, guest, europe-users"/>
   <permission type="send" roles="admin, europe-users"/>
   <permission type="consume" roles="admin, europe-users"/>
</security-setting>

Given the fact that hornetq-jms.xml includes:

connection.factory=/ConnectionFactory

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory

java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory

java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

java.naming.provider.url=$BROKER_IP:$BROKER_PORT

java.naming.provider.url=tcp://$BROKER_IP:$BROKER_PORT

or for a failover setup:

java.naming.provider.url=failover:\(tcp://$BROKER_MASTER_IP:$BROKER_MASTER_PORT,tcp://$BROKER_SLAVE_IP:$BROKER_SLAVE_PORT)

<security-enabled>false</security-enabled>

/paging</paging-directory>

/bindings</bindings-directory>

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

/journal</journal-directory>

If you do not wish clients to be able to specify their own connection TTL, you can override all values used by a global value set on the server side. This can be done by specifying the connection-ttl-override attribute in the server side configuration. The default value for connection-ttl-override is -1 which means "do not override" (i.e. let clients use their own values).

<address-settings>
<!--default for catch all -->
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<max-delivery-attempts>10</max-delivery-attempts>
<redelivery-delay>1000</redelivery-delay>
<max-size-bytes>104857600</max-size-bytes>
<page-size-bytes>10485760</page-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
</address-setting>
</address-settings>

Parameter

Explanation

-v /var/artemis-data/etc-override-master:/var/lib/artemis/etc-override

Creates a shared volume between the container and the host machine so that when the container starts it is able to read multiple broker XML files.

Multiple files with snippets of configuration can be dropped in the /var/lib/artemis/etc-override volume. Those configuration files must be named following the name convention broker-{{num}}.xml where num is a numeric representation of the snippet. The configuration files will be merged with the default configuration. An alphabetical precedence of the file names will be considered for the merge and in case of collision, the latest change will be treated as final.

-v /opt/amq/sharedstore:/var/lib/artemis/data

Creates a shared volume between the container and the host machine so that when the container starts it is able to read and store the JMS data files/folders. This is very useful when you need to share data between master and slave node. If these nodes run on different machines you should share this folder through NFS.

-e 'ARTEMIS_USERNAME=admin'

-e 'ARTEMIS_PASSWORD=admin'

Username and password for the dashboard at port 8161 for the master node and 8162 for the slave node.

-e 'ENABLE_JMX=true'

Due to the JMX's nature, often with dynamics ports for RMI and the need having configured the public IP address to reach the RMI server. It is discouraged to use JMX in Docker. Although in certain scenarios, it could be advisable, as when deploying in a container orchestrator such as Kubernetes or Mesos, and deploying alongside this container a sidecar. For such cases, the following environment variable could be used: ENABLE_JMX.

-e 'JAVA_OPTS=-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=*'

Also explained above. Will pass additional java options (for security) to the artemis runtime.

-p 8161:8161 \
-p 61616:61616 \

-p 8162:8161 \
-p 61617:61616 \

Master Node listens at: web dashboard 8161, JMS 61616

Slave Node listens at: web dashboard 8162, JMS 61617