Link: https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/configuring-messaging-applications/#colocated_ha_topology_backup

Colocated topology as described in [1] is not supported. This new Artemis feature creates Backup server automatically. However it is possible to configure Backup servers manually what is supported and tested configuration.

Basically if you want to configure such topology you have to create two Artemis brokers for each EAP server, one Live and one Backup.

<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
  <server name="default">
    ...
  </server>
  <server name="backup">
    ...
  </server>
<subsystem>

Example of such configuration you can find for example in the discussion [2].

Be aware that you have to properly configure paths for journal related directories. If you configure shared-store colocated topology, the Live from server 1 and Backup from server 2 have to point to the same journal. The same is true for Live from server 2 and Backup from server 1.

If you configure replicated colocated topology, each Artemis server has to have its own journal. In this case you will have 4 journals. You have to specify them explicitly, because by default both Artemis brokers in one server point to the same journal standalone/data/activemq/. You also have to properly configure group-name of servers. Live from server 1 and Backup from server 2 have to have the same group-name. The same is true for Live from server 2 and Backup from server 1.

[1] https://activemq.apache.org/artemis/docs/1.1.0/ha.html#colocated-backup-servers
[2] https://developer.jboss.org/message/952462#952462