You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by grishezz <gr...@gmail.com> on 2016/11/29 09:26:48 UTC

H/A colocated replication environment not working as expected

Hello,

I am trying to set-up the following environment and have ran into
difficulties:

H/A cluster of 2 servers: server0 & server1 replication=colocated
master/slave, and message-load-balancing=OFF.

Running the following scenario:

1) start server0
2) start server1
3) start consumer0 (connected to server0)
4) start consumer1 (connected to server1)
5) start producer0 (connected to server0)
6) producer0 sends 100 messages to exampleQueue
7) consumer0 is blocked on the first message read using debugger
8) kill server0

Now, I expected these 100 messages that were not yet acknowledged to become
available on server1 (as server0 backup is supposed to be there). However
client1 is receiving no messages (and I can't see them via the jmx console
either - though here I wasn't sure if they should actually move to the live
exampleQueue on server1).

Below are the 2 logs and a configuration of one of the servers (the other is
an exact mirror image). I wonder if the "Connection failed with
failedOver=false" message might have something to do with the scenario not
working as expected. I have tried many different config permutations and
have gone through the documentation several times... I hope I am just
missing some minor detail.

Help would be greatly appreciated!

============
server0 log:
============
19:01:58,344 WARN  [org.apache.activemq.artemis.core.server] AMQ222018: AIO
was not located on this platform, it will fall back to using pure Java NIO.
If your platform is Linux, install LibAIO to enable the AIO journal
19:01:58,399 WARN  [org.apache.activemq.artemis.core.server] AMQ222018: AIO
was not located on this platform, it will fall back to using pure Java NIO.
If your platform is Linux, install LibAIO to enable the AIO journal
19:01:58,441 INFO  [org.apache.activemq.artemis.integration.bootstrap]
AMQ101000: Starting ActiveMQ Artemis Server
19:02:00,364 INFO  [org.apache.activemq.artemis.core.server] AMQ221000: live
Message Broker is starting with configuration Broker Configuration
(clustered=true,journalDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/journal,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/bindings,largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/largemessages,pagingDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/paging)
19:02:00,391 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
Using NIO Journal
19:02:00,420 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
Security risk! Apache ActiveMQ Artemis is running with the default cluster
admin user and default password. Please see the cluster chapter in the
ActiveMQ Artemis User Guide for instructions on how to change this.
19:02:00,457 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
19:02:00,459 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
AMQP
19:02:00,461 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
for: HORNETQ
19:02:00,463 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
MQTT
19:02:00,464 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-openwire-protocol]. Adding protocol support
for: OPENWIRE
19:02:00,465 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-stomp-protocol]. Adding protocol support
for: STOMP
19:02:00,737 INFO  [org.apache.activemq.artemis.core.server] AMQ221003:
Deploying queue jms.queue.exampleQueue
19:02:00,766 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:02:00,767 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:02:00,998 INFO  [org.apache.activemq.artemis.core.server] AMQ221020:
Started Acceptor at localhost:61616 for protocols
[CORE,MQTT,AMQP,HORNETQ,STOMP,OPENWIRE]
19:02:00,999 INFO  [org.apache.activemq.artemis.core.server] AMQ221007:
Server is now live
19:02:00,999 INFO  [org.apache.activemq.artemis.core.server] AMQ221001:
Apache ActiveMQ Artemis Message Broker version 1.5.0 [localhost,
nodeID=60b03b78-b58c-11e6-937d-b8a720524153] 
19:02:05,096 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue
sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153 in AddressSettings
19:02:05,096 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue
sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153 in AddressSettings
19:02:05,182 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue
notif.638d929a-b58c-11e6-ace0-b8a720524153.ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
in AddressSettings
19:02:05,183 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue
notif.638d929a-b58c-11e6-ace0-b8a720524153.ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
in AddressSettings
19:02:05,224 INFO  [org.apache.activemq.artemis.core.server] AMQ221027:
Bridge ClusterConnectionBridge@79c09e99
[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
queue=QueueImpl[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153]]@177c753c
targetConnector=ServerLocatorImpl
(identity=(Cluster-connection-bridge::ClusterConnectionBridge@79c09e99
[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
queue=QueueImpl[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153]]@177c753c
targetConnector=ServerLocatorImpl
[initialConnectors=[TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61617&host=localhost],
discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1297836716[nodeUUID=60b03b78-b58c-11e6-937d-b8a720524153,
connector=TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61616&host=localhost, address=jms,
server=ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153]))
[initialConnectors=[TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61617&host=localhost], discoveryGroupConfiguration=null]] is connected
19:02:06,074 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
backup Message Broker is starting with configuration Broker Configuration
(clustered=true,journalDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/journalcolocated_backup_01,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/bindingscolocated_backup_01,largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/largemessagescolocated_backup_01,pagingDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/pagingcolocated_backup_01)
19:02:06,083 INFO  [org.apache.activemq.artemis.core.server] AMQ221049:
Activating Replica for node: 63157c62-b58c-11e6-ace0-b8a720524153
19:02:06,086 INFO  [org.apache.activemq.artemis.core.server] AMQ222162:
Moving data directory
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data\server0\data\messaging\journalcolocated_backup_01
to
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data\server0\data\messaging\journalcolocated_backup_01\oldreplica.1
19:02:06,088 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
Using NIO Journal
19:02:06,088 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
Security risk! Apache ActiveMQ Artemis is running with the default cluster
admin user and default password. Please see the cluster chapter in the
ActiveMQ Artemis User Guide for instructions on how to change this.
19:02:06,089 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
19:02:06,090 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
AMQP
19:02:06,091 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
for: HORNETQ
19:02:06,092 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
MQTT
19:02:06,094 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-openwire-protocol]. Adding protocol support
for: OPENWIRE
19:02:06,096 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-stomp-protocol]. Adding protocol support
for: STOMP
19:02:06,104 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
live to fail before it gets active
19:02:06,920 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
Backup server
ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153 is
synchronized with live-server.
19:02:06,929 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
backup announced
19:02:07,265 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-data-2.amq id = 2, recordID
= 2) (size=10,485,760) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data\server0\data\messaging\journal\activemq-data-2.amq
19:02:07,776 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-bindings-4.bindings id = 1,
recordID = 1) (size=1,048,576) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data\server0\data\messaging\bindings\activemq-bindings-4.bindings
19:02:07,785 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-bindings-2.bindings id = 2,
recordID = 2) (size=1,048,576) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server0\data\server0\data\messaging\bindings\activemq-bindings-2.bindings
19:03:15,030 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue jms.queue.HBQueue in
AddressSettings
19:03:15,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue jms.queue.HBQueue in AddressSettings
19:04:51,861 INFO  [org.apache.activemq.artemis.core.server] AMQ221002:
Apache ActiveMQ Artemis Message Broker version 1.5.0
[63157c62-b58c-11e6-ace0-b8a720524153] stopped, uptime 2 minutes
19:04:51,890 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
stopped bridge sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
19:04:51,998 INFO  [org.apache.activemq.artemis.core.server] AMQ221002:
Apache ActiveMQ Artemis Message Broker version 1.5.0
[60b03b78-b58c-11e6-937d-b8a720524153] stopped, uptime 2 minutes

============
server1 log:
============
19:02:02,394 WARN  [org.apache.activemq.artemis.core.server] AMQ222018: AIO
was not located on this platform, it will fall back to using pure Java NIO.
If your platform is Linux, install LibAIO to enable the AIO journal
19:02:02,438 WARN  [org.apache.activemq.artemis.core.server] AMQ222018: AIO
was not located on this platform, it will fall back to using pure Java NIO.
If your platform is Linux, install LibAIO to enable the AIO journal
19:02:02,485 INFO  [org.apache.activemq.artemis.integration.bootstrap]
AMQ101000: Starting ActiveMQ Artemis Server
19:02:04,388 INFO  [org.apache.activemq.artemis.core.server] AMQ221000: live
Message Broker is starting with configuration Broker Configuration
(clustered=true,journalDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/journal,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/bindings,largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/largemessages,pagingDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/paging)
19:02:04,415 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
Using NIO Journal
19:02:04,442 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
Security risk! Apache ActiveMQ Artemis is running with the default cluster
admin user and default password. Please see the cluster chapter in the
ActiveMQ Artemis User Guide for instructions on how to change this.
19:02:04,479 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
19:02:04,482 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
AMQP
19:02:04,483 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
for: HORNETQ
19:02:04,485 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
MQTT
19:02:04,486 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-openwire-protocol]. Adding protocol support
for: OPENWIRE
19:02:04,487 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-stomp-protocol]. Adding protocol support
for: STOMP
19:02:04,744 INFO  [org.apache.activemq.artemis.core.server] AMQ221003:
Deploying queue jms.queue.exampleQueue
19:02:04,778 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:02:04,778 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:02:05,044 INFO  [org.apache.activemq.artemis.core.server] AMQ221020:
Started Acceptor at localhost:61617 for protocols
[CORE,MQTT,AMQP,HORNETQ,STOMP,OPENWIRE]
19:02:05,045 INFO  [org.apache.activemq.artemis.core.server] AMQ221007:
Server is now live
19:02:05,046 INFO  [org.apache.activemq.artemis.core.server] AMQ221001:
Apache ActiveMQ Artemis Message Broker version 1.5.0 [localhost,
nodeID=63157c62-b58c-11e6-ace0-b8a720524153] 
19:02:05,117 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue
sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153 in AddressSettings
19:02:05,117 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue
sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153 in AddressSettings
19:02:05,181 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue
notif.638d1cb0-b58c-11e6-937d-b8a720524153.ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
in AddressSettings
19:02:05,182 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue
notif.638d1cb0-b58c-11e6-937d-b8a720524153.ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
in AddressSettings
19:02:05,222 INFO  [org.apache.activemq.artemis.core.server] AMQ221027:
Bridge ClusterConnectionBridge@53d3b1d5
[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
queue=QueueImpl[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153]]@17875087
targetConnector=ServerLocatorImpl
(identity=(Cluster-connection-bridge::ClusterConnectionBridge@53d3b1d5
[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
queue=QueueImpl[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153]]@17875087
targetConnector=ServerLocatorImpl
[initialConnectors=[TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61616&host=localhost],
discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1297836716[nodeUUID=63157c62-b58c-11e6-ace0-b8a720524153,
connector=TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61617&host=localhost, address=jms,
server=ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153]))
[initialConnectors=[TransportConfiguration(name=netty-connector,
factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
?port=61616&host=localhost], discoveryGroupConfiguration=null]] is connected
19:02:06,274 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-data-2.amq id = 2, recordID
= 2) (size=10,485,760) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data\server0\data\messaging\journal\activemq-data-2.amq
19:02:06,651 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-bindings-4.bindings id = 1,
recordID = 1) (size=1,048,576) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data\server0\data\messaging\bindings\activemq-bindings-4.bindings
19:02:06,659 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
Replication: sending JournalFileImpl: (activemq-bindings-2.bindings id = 2,
recordID = 2) (size=1,048,576) to backup. NIOSequentialFile
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data\server0\data\messaging\bindings\activemq-bindings-2.bindings
19:02:07,046 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
backup Message Broker is starting with configuration Broker Configuration
(clustered=true,journalDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/journalcolocated_backup_01,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/bindingscolocated_backup_01,largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/largemessagescolocated_backup_01,pagingDirectory=C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/pagingcolocated_backup_01)
19:02:07,054 INFO  [org.apache.activemq.artemis.core.server] AMQ221049:
Activating Replica for node: 60b03b78-b58c-11e6-937d-b8a720524153
19:02:07,056 INFO  [org.apache.activemq.artemis.core.server] AMQ222162:
Moving data directory
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data\server0\data\messaging\journalcolocated_backup_01
to
C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\target\server1\data\server0\data\messaging\journalcolocated_backup_01\oldreplica.1
19:02:07,059 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
Using NIO Journal
19:02:07,059 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
Security risk! Apache ActiveMQ Artemis is running with the default cluster
admin user and default password. Please see the cluster chapter in the
ActiveMQ Artemis User Guide for instructions on how to change this.
19:02:07,060 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-server]. Adding protocol support for: CORE
19:02:07,061 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-amqp-protocol]. Adding protocol support for:
AMQP
19:02:07,063 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
for: HORNETQ
19:02:07,064 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for:
MQTT
19:02:07,065 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-openwire-protocol]. Adding protocol support
for: OPENWIRE
19:02:07,066 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
Protocol module found: [artemis-stomp-protocol]. Adding protocol support
for: STOMP
19:02:07,076 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
live to fail before it gets active
19:02:08,015 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
Backup server
ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 is
synchronized with live-server.
19:02:08,022 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
backup announced
19:04:21,859 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue jms.queue.HBQueue in
AddressSettings
19:04:21,859 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue jms.queue.HBQueue in AddressSettings
19:04:51,830 WARN  [org.apache.activemq.artemis.core.server] AMQ222092:
Connection to the backup node failed, removing replication now:
ActiveMQRemoteDisconnectException[errorType=REMOTE_DISCONNECT message=null]
	at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:533)
[artemis-server-1.5.0.jar:1.5.0]
	at
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor$Listener.connectionDestroyed(NettyAcceptor.java:681)
[artemis-server-1.5.0.jar:1.5.0]
	at
org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelInactive(ActiveMQChannelHandler.java:75)
[artemis-core-client-1.5.0.jar:1.5.0]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:255)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:241)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:234)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:360)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:325)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:255)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:241)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:234)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1329)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:255)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:241)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:908)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:744)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)
[netty-all-4.1.5.Final.jar:4.1.5.Final]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_74]
19:04:51,873 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:51,883 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:51,885 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
Connection failed with failedOver=false
19:04:51,954 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
Connection failed with failedOver=false
19:04:51,961 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
stopped bridge sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
19:04:51,982 INFO  [org.apache.activemq.artemis.core.server] AMQ221037:
ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 to
become 'live'
19:04:51,983 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED]
19:04:52,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:04:52,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue jms.queue.exampleQueue in
AddressSettings
19:04:52,034 WARN  [org.apache.activemq.artemis.core.server] AMQ222165: No
Dead Letter Address configured for queue
sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153 in AddressSettings
19:04:52,035 WARN  [org.apache.activemq.artemis.core.server] AMQ222166: No
Expiry Address configured for queue
sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153 in AddressSettings
19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down 0
messages total.

===========
borker.xml:
===========
<?xml version='1.0'?>
<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xmlns="urn:activemq"
               xsi:schemaLocation="urn:activemq /schema/artemis-server.xsd">

    <jms xmlns="urn:activemq:jms">
        
        <queue name="exampleQueue"/>
    </jms>

    <core xmlns="urn:activemq:core">

       
<bindings-directory>${data.dir}/server0/data/messaging/bindings</bindings-directory>

       
<journal-directory>${data.dir}/server0/data/messaging/journal</journal-directory>

       
<large-messages-directory>${data.dir}/server0/data/messaging/largemessages</large-messages-directory>

       
<paging-directory>${data.dir}/server0/data/messaging/paging</paging-directory>
        

        <connectors>
            <connector name="invm-connector">vm://0</connector>
            <connector
name="netty-connector">tcp://localhost:61616</connector>
            
            <connector
name="server1-connector">tcp://localhost:61617</connector>
        </connectors>

        
        <acceptors>
            <acceptor name="invm-acceptor">vm://0</acceptor>
            <acceptor name="netty-acceptor">tcp://localhost:61616</acceptor>
        </acceptors>

        
        <ha-policy>
            <replication>
                <colocated>
                    <max-backups>2</max-backups>
                    <request-backup>true</request-backup>
                   
<backup-request-retry-interval>1000</backup-request-retry-interval>
                    <excludes>
                        <connector-ref>invm-connector</connector-ref>
                        <connector-ref>server1-connector</connector-ref>
                        <connector-ref>netty-connector</connector-ref>
                    </excludes>
                    <master/>
                    <slave>
                        <scale-down>
                            <connectors>
                               
<connector-ref>invm-connector</connector-ref>
                            </connectors>
                        </scale-down>
                    </slave>
                </colocated>
            </replication>
        </ha-policy>

        <cluster-connections>
            <cluster-connection name="my-cluster">
                <address>jms</address>
                <connector-ref>netty-connector</connector-ref>
                <retry-interval>500</retry-interval>
                <use-duplicate-detection>true</use-duplicate-detection>
                <message-load-balancing>OFF</message-load-balancing>
                <max-hops>1</max-hops>
                <static-connectors>
                    <connector-ref>server1-connector</connector-ref>
                </static-connectors>
            </cluster-connection>
        </cluster-connections>

        

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

    </core>
</configuration>





--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

What would be server2 in the topology I described? What configuration / which
actions do I need to take to make the messages stored on server1 (i.e. the
backup server colocated with server1) be available for consumption?



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719589.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

Can you make sue your messages are persistent. If they are try turning
scaledown off and see if there are any messages in the journal when the
back up comes live. If you are still having problems send me you're
configuration and I will have a look tomorrow

Andy

On 1 December 2016 at 17:07, grishezz [via ActiveMQ] <
ml-node+s2283324n4719679h29@n4.nabble.com> wrote:

> You can see the entire logs, as well as the configuration I used in the
> first post in this thread, I am also copying the relevant parts here:
>
> server0:
> =====
> 19:02:06,104 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:06,920 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
> is synchronized with live-server.
> 19:02:06,929 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
>
> server1:
> =====
> 19:02:07,076 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:08,015 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
> is synchronized with live-server.
> 19:02:08,022 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
> ...
> 19:04:51,883 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,885 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,954 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,961 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
> stopped bridge sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
> 19:04:51,982 INFO  [org.apache.activemq.artemis.core.server] AMQ221037:
> ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 to
> become 'live'
> 19:04:51,983 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> ...
> 19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down
> 0 messages total.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719679.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719683.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

You can see the entire logs, as well as the configuration I used in the first
post in this thread, I am also copying the relevant parts here:

server0:
=====
19:02:06,104 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
live to fail before it gets active 
19:02:06,920 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
Backup server
ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153 is
synchronized with live-server. 
19:02:06,929 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
backup announced 

server1:
=====
19:02:07,076 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
live to fail before it gets active 
19:02:08,015 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
Backup server
ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 is
synchronized with live-server. 
19:02:08,022 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
backup announced 
...
19:04:51,883 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED] 
19:04:51,885 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
Connection failed with failedOver=false 
19:04:51,954 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
Connection failed with failedOver=false 
19:04:51,961 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
stopped bridge sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153 
19:04:51,982 INFO  [org.apache.activemq.artemis.core.server] AMQ221037:
ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 to
become 'live' 
19:04:51,983 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
Connection failure has been detected: AMQ119015: The connection was
disconnected because of server shutdown [code=DISCONNECTED] 
...
19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down 0
messages total.




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719679.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

couple of questions

1. do you see logs in each broker saying that a backup server has been
started and announced?
2. when you kill the server1 do you see logs in server2 saying that failure
has been detected?



On 1 December 2016 at 14:51, grishezz [via ActiveMQ] <
ml-node+s2283324n4719668h88@n4.nabble.com> wrote:

> I did. This example is for shared-storage. My scenario is not fit for
> shared-storage.
>
> Honestly, I am beginning to doubt if it even works at all (perhaps a bug
> was introduced into the network-based replication mechanism at some
> point?). Are there any live systems actually using it with either 1.4 or
> 1.5?
>
> I would love to see a working example of the scenario I described above in
> an integration test for example...
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719668.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719674.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

I did. This example is for shared-storage. My scenario is not fit for
shared-storage.

Honestly, I am beginning to doubt if it even works at all (perhaps a bug was
introduced into the network-based replication mechanism at some point?). Are
there any live systems actually using it with either 1.4 or 1.5?

I would love to see a working example of the scenario I described above in
an integration test for example...



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719668.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

take a look at
https://github.com/apache/activemq-artemis/tree/master/examples/features/ha/colocated-failover-scale-down

On 30 November 2016 at 08:53, grishezz [via ActiveMQ] <
ml-node+s2283324n4719600h80@n4.nabble.com> wrote:

> Well, I see data files are indeed created under the server1 colocated
> backup. And the configuration above includes a <scale-down> clause. Other
> than that, I am not sure what does it mean to "make sure" - can I look at
> some information/properties via the jmx interface?
>
> As you can see in the attached logs, it says:
> 19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down
> 0 messages total.
>
> But why these 100 messages are not scaled down, I do not know.
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719600.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719601.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

Well, I see data files are indeed created under the server1 colocated backup.
And the configuration above includes a <scale-down> clause. Other than that,
I am not sure what does it mean to "make sure" - can I look at some
information/properties via the jmx interface?

As you can see in the attached logs, it says:
19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down 0
messages total. 

But why these 100 messages are not scaled down, I do not know.



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719600.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

you need to make sure that a backup is created colocated with server1 and
that it scales down.

On 29 November 2016 at 22:09, Justin Bertram-2 [via ActiveMQ] <
ml-node+s2283324n4719591h1@n4.nabble.com> wrote:

> Sorry for the confusion.  The <failover-on-shutdown> option is only
> available for shared-storage.  The fail-over semantics for replication
> don't use that parameter.  Carry on.
>
>
> Justin
>
> ----- Original Message -----
> From: "grishezz" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=4719591&i=0>>
> To: [hidden email] <http:///user/SendEmail.jtp?type=node&node=4719591&i=1>
> Sent: Tuesday, November 29, 2016 4:01:55 PM
> Subject: Re: H/A colocated replication environment not working as expected
>
> I only saw the <failover-on-shutdown> option available for shared-storage.
> Can I somehow turn it on for replicated-colocated topology?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/H-A-colocated-replication-environment-not-working-as-expected-
> tp4719539p4719590.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719591.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719594.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by Justin Bertram <jb...@apache.com>.

Sorry for the confusion.  The <failover-on-shutdown> option is only available for shared-storage.  The fail-over semantics for replication don't use that parameter.  Carry on.

Justin

----- Original Message -----
From: "grishezz" <gr...@gmail.com>
To: users@activemq.apache.org
Sent: Tuesday, November 29, 2016 4:01:55 PM
Subject: Re: H/A colocated replication environment not working as expected

I only saw the <failover-on-shutdown> option available for shared-storage.
Can I somehow turn it on for replicated-colocated topology?

--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719590.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

I only saw the <failover-on-shutdown> option available for shared-storage.
Can I somehow turn it on for replicated-colocated topology?



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719590.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by Justin Bertram <jb...@apache.com>.

One more quick point...

Stopping a server gracefully (e.g. using CTRL-C) will not trigger fail-over unless <failover-on-shutdown> is true.  In general I recommend using a method like 'kill -9 <pid>' to test fail-over.


Justin

----- Original Message -----
From: "andytaylor" <an...@gmail.com>
To: users@activemq.apache.org
Sent: Tuesday, November 29, 2016 8:47:36 AM
Subject: Re: H/A colocated replication environment not working as expected

server0 is backed up by the backup server that is colocated with server1,
not server1 itself. Server2 can either be configured to start as an actual
live or scaledown to the live server, if the latter is configured you
should see the message in server1, if not they will be in the backup
started on server1 when it starts

On 29 November 2016 at 14:18, grishezz [via ActiveMQ] <
ml-node+s2283324n4719546h6@n4.nabble.com> wrote:

> Right. But now I kill server0 (with all 100 messages) before any messages
> were consumed. My expectation is for these messages to "migrate" to the
> other live server (server1), so that they could be consumed from there.
>
> I am saying "migrate", but really at this moment server0 is already dead,
> so what I thought is supposed to happen is for server1 to detect the
> failure of server0 and thus "restore" those 100 messages it was holding as
> a backup and make them available for consumption. Am I mistaken in this
> expectation?
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719546.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719550.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

server0 is backed up by the backup server that is colocated with server1,
not server1 itself. Server2 can either be configured to start as an actual
live or scaledown to the live server, if the latter is configured you
should see the message in server1, if not they will be in the backup
started on server1 when it starts

On 29 November 2016 at 14:18, grishezz [via ActiveMQ] <
ml-node+s2283324n4719546h6@n4.nabble.com> wrote:

> Right. But now I kill server0 (with all 100 messages) before any messages
> were consumed. My expectation is for these messages to "migrate" to the
> other live server (server1), so that they could be consumed from there.
>
> I am saying "migrate", but really at this moment server0 is already dead,
> so what I thought is supposed to happen is for server1 to detect the
> failure of server0 and thus "restore" those 100 messages it was holding as
> a backup and make them available for consumption. Am I mistaken in this
> expectation?
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719546.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719550.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

Right. But now I kill server0 (with all 100 messages) before any messages
were consumed. My expectation is for these messages to "migrate" to the
other live server (server1), so that they could be consumed from there. 

I am saying "migrate", but really at this moment server0 is already dead, so
what I thought is supposed to happen is for server1 to detect the failure of
server0 and thus "restore" those 100 messages it was holding as a backup and
make them available for consumption. Am I mistaken in this expectation?



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719546.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

Then I would expect to see 100 messages at the broker you sent to and none
on the other live broker

On 29 November 2016 at 12:34, grishezz [via ActiveMQ] <
ml-node+s2283324n4719543h13@n4.nabble.com> wrote:

> In this scenario message load balancing is disabled.
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539p4719543.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719544.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by grishezz <gr...@gmail.com>.

In this scenario message load balancing is disabled.



--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719543.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: H/A colocated replication environment not working as expected

Posted by andytaylor <an...@gmail.com>.

Im not 100% sure of your topology, however leaving backups out of it I
would expect to see 50 messages on server0 and 50 on server1 if you have
load balancing enabled.

On 29 November 2016 at 09:26, grishezz [via ActiveMQ] <
ml-node+s2283324n4719539h89@n4.nabble.com> wrote:

> Hello,
>
> I am trying to set-up the following environment and have ran into
> difficulties:
>
> H/A cluster of 2 servers: server0 & server1 replication=colocated
> master/slave, and message-load-balancing=OFF.
>
> Running the following scenario:
>
> 1) start server0
> 2) start server1
> 3) start consumer0 (connected to server0)
> 4) start consumer1 (connected to server1)
> 5) start producer0 (connected to server0)
> 6) producer0 sends 100 messages to exampleQueue
> 7) consumer0 is blocked on the first message read using debugger
> 8) kill server0
>
> Now, I expected these 100 messages that were not yet acknowledged to
> become available on server1 (as server0 backup is supposed to be there).
> However client1 is receiving no messages (and I can't see them via the jmx
> console either - though here I wasn't sure if they should actually move to
> the live exampleQueue on server1).
>
> Below are the 2 logs and a configuration of one of the servers (the other
> is an exact mirror image). I wonder if the "Connection failed with
> failedOver=false" message might have something to do with the scenario not
> working as expected. I have tried many different config permutations and
> have gone through the documentation several times... I hope I am just
> missing some minor detail.
>
> Help would be greatly appreciated!
>
> ============
> server0 log:
> ============
> 19:01:58,344 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:01:58,399 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:01:58,441 INFO  [org.apache.activemq.artemis.integration.bootstrap]
> AMQ101000: Starting ActiveMQ Artemis Server
> 19:02:00,364 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
> live Message Broker is starting with configuration Broker Configuration
> (clustered=true,journalDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/journal,bindingsDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/bindings,
> largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\
> examples\features\ha\mark-poc\target\server0\data/server0/
> data/messaging/largemessages,pagingDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/paging)
> 19:02:00,391 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
> Using NIO Journal
> 19:02:00,420 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
> Security risk! Apache ActiveMQ Artemis is running with the default cluster
> admin user and default password. Please see the cluster chapter in the
> ActiveMQ Artemis User Guide for instructions on how to change this.
> 19:02:00,457 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 19:02:00,459 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support
> for: AMQP
> 19:02:00,461 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 19:02:00,463 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support
> for: MQTT
> 19:02:00,464 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 19:02:00,465 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support
> for: STOMP
> 19:02:00,737 INFO  [org.apache.activemq.artemis.core.server] AMQ221003:
> Deploying queue jms.queue.exampleQueue
> 19:02:00,766 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:00,767 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:00,998 INFO  [org.apache.activemq.artemis.core.server] AMQ221020:
> Started Acceptor at localhost:61616 for protocols
> [CORE,MQTT,AMQP,HORNETQ,STOMP,OPENWIRE]
> 19:02:00,999 INFO  [org.apache.activemq.artemis.core.server] AMQ221007:
> Server is now live
> 19:02:00,999 INFO  [org.apache.activemq.artemis.core.server] AMQ221001:
> Apache ActiveMQ Artemis Message Broker version 1.5.0 [localhost,
> nodeID=60b03b78-b58c-11e6-937d-b8a720524153]
> 19:02:05,096 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:02:05,096 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:02:05,182 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue notif.638d929a-b58c-11e6-ace0-
> b8a720524153.ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:02:05,183 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue notif.638d929a-b58c-11e6-ace0-
> b8a720524153.ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:02:05,224 INFO  [org.apache.activemq.artemis.core.server] AMQ221027:
> Bridge ClusterConnectionBridge@79c09e99 [name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
> queue=QueueImpl[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::
> serverUUID=60b03b78-b58c-11e6-937d-b8a720524153]]@177c753c
> targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::
> ClusterConnectionBridge@79c09e99 [name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
> queue=QueueImpl[name=sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153,
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::
> serverUUID=60b03b78-b58c-11e6-937d-b8a720524153]]@177c753c
> targetConnector=ServerLocatorImpl [initialConnectors=[
> TransportConfiguration(name=netty-connector, factory=org-apache-activemq-
> artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61617&host=localhost], discoveryGroupConfiguration=
> null]]::ClusterConnectionImpl@1297836716[nodeUUID=60b03b78-b58c-11e6-937d-b8a720524153,
> connector=TransportConfiguration(name=netty-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61616&host=localhost, address=jms, server=ActiveMQServerImpl::
> serverUUID=60b03b78-b58c-11e6-937d-b8a720524153])) [initialConnectors=[
> TransportConfiguration(name=netty-connector, factory=org-apache-activemq-
> artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61617&host=localhost], discoveryGroupConfiguration=null]] is
> connected
> 19:02:06,074 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
> backup Message Broker is starting with configuration Broker Configuration
> (clustered=true,journalDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server0\data/server0/data/messaging/journalcolocated_
> backup_01,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.
> 0\examples\features\ha\mark-poc\target\server0\data/
> server0/data/messaging/bindingscolocated_backup_01,
> largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\
> examples\features\ha\mark-poc\target\server0\data/server0/data/messaging/
> largemessagescolocated_backup_01,pagingDirectory=C:\dev_
> temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\
> target\server0\data/server0/data/messaging/pagingcolocated_backup_01)
> 19:02:06,083 INFO  [org.apache.activemq.artemis.core.server] AMQ221049:
> Activating Replica for node: 63157c62-b58c-11e6-ace0-b8a720524153
> 19:02:06,086 INFO  [org.apache.activemq.artemis.core.server] AMQ222162:
> Moving data directory C:\dev_temp\apache-artemis-1.
> 5.0\examples\features\ha\mark-poc\target\server0\data\
> server0\data\messaging\journalcolocated_backup_01 to
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server0\data\server0\data\messaging\journalcolocated_backup_01\oldreplica.1
>
> 19:02:06,088 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
> Using NIO Journal
> 19:02:06,088 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
> Security risk! Apache ActiveMQ Artemis is running with the default cluster
> admin user and default password. Please see the cluster chapter in the
> ActiveMQ Artemis User Guide for instructions on how to change this.
> 19:02:06,089 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 19:02:06,090 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support
> for: AMQP
> 19:02:06,091 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 19:02:06,092 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support
> for: MQTT
> 19:02:06,094 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 19:02:06,096 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support
> for: STOMP
> 19:02:06,104 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:06,920 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server ActiveMQServerImpl::serverUUID=63157c62-b58c-11e6-ace0-b8a720524153
> is synchronized with live-server.
> 19:02:06,929 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
> 19:02:07,265 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-data-2.amq id = 2, recordID
> = 2) (size=10,485,760) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server0\data\server0\data\messaging\journal\activemq-data-2.amq
>
> 19:02:07,776 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-bindings-4.bindings id = 1,
> recordID = 1) (size=1,048,576) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server0\data\server0\data\messaging\
> bindings\activemq-bindings-4.bindings
> 19:02:07,785 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-bindings-2.bindings id = 2,
> recordID = 2) (size=1,048,576) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server0\data\server0\data\messaging\
> bindings\activemq-bindings-2.bindings
> 19:03:15,030 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.HBQueue in
> AddressSettings
> 19:03:15,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.HBQueue in AddressSettings
> 19:04:51,861 INFO  [org.apache.activemq.artemis.core.server] AMQ221002:
> Apache ActiveMQ Artemis Message Broker version 1.5.0
> [63157c62-b58c-11e6-ace0-b8a720524153] stopped, uptime 2 minutes
> 19:04:51,890 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
> stopped bridge sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
> 19:04:51,998 INFO  [org.apache.activemq.artemis.core.server] AMQ221002:
> Apache ActiveMQ Artemis Message Broker version 1.5.0
> [60b03b78-b58c-11e6-937d-b8a720524153] stopped, uptime 2 minutes
>
> ============
> server1 log:
> ============
> 19:02:02,394 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:02:02,438 WARN  [org.apache.activemq.artemis.core.server] AMQ222018:
> AIO was not located on this platform, it will fall back to using pure Java
> NIO. If your platform is Linux, install LibAIO to enable the AIO journal
> 19:02:02,485 INFO  [org.apache.activemq.artemis.integration.bootstrap]
> AMQ101000: Starting ActiveMQ Artemis Server
> 19:02:04,388 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
> live Message Broker is starting with configuration Broker Configuration
> (clustered=true,journalDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server1\data/server0/data/messaging/journal,bindingsDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server1\data/server0/data/messaging/bindings,
> largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\
> examples\features\ha\mark-poc\target\server1\data/server0/
> data/messaging/largemessages,pagingDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server1\data/server0/data/messaging/paging)
> 19:02:04,415 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
> Using NIO Journal
> 19:02:04,442 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
> Security risk! Apache ActiveMQ Artemis is running with the default cluster
> admin user and default password. Please see the cluster chapter in the
> ActiveMQ Artemis User Guide for instructions on how to change this.
> 19:02:04,479 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 19:02:04,482 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support
> for: AMQP
> 19:02:04,483 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 19:02:04,485 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support
> for: MQTT
> 19:02:04,486 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 19:02:04,487 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support
> for: STOMP
> 19:02:04,744 INFO  [org.apache.activemq.artemis.core.server] AMQ221003:
> Deploying queue jms.queue.exampleQueue
> 19:02:04,778 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:04,778 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:02:05,044 INFO  [org.apache.activemq.artemis.core.server] AMQ221020:
> Started Acceptor at localhost:61617 for protocols
> [CORE,MQTT,AMQP,HORNETQ,STOMP,OPENWIRE]
> 19:02:05,045 INFO  [org.apache.activemq.artemis.core.server] AMQ221007:
> Server is now live
> 19:02:05,046 INFO  [org.apache.activemq.artemis.core.server] AMQ221001:
> Apache ActiveMQ Artemis Message Broker version 1.5.0 [localhost,
> nodeID=63157c62-b58c-11e6-ace0-b8a720524153]
> 19:02:05,117 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
> in AddressSettings
> 19:02:05,117 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
> in AddressSettings
> 19:02:05,181 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue notif.638d1cb0-b58c-11e6-937d-
> b8a720524153.ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
> in AddressSettings
> 19:02:05,182 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue notif.638d1cb0-b58c-11e6-937d-
> b8a720524153.ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
> in AddressSettings
> 19:02:05,222 INFO  [org.apache.activemq.artemis.core.server] AMQ221027:
> Bridge ClusterConnectionBridge@53d3b1d5 [name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
> queue=QueueImpl[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::
> serverUUID=63157c62-b58c-11e6-ace0-b8a720524153]]@17875087
> targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::
> ClusterConnectionBridge@53d3b1d5 [name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
> queue=QueueImpl[name=sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153,
> postOffice=PostOfficeImpl [server=ActiveMQServerImpl::
> serverUUID=63157c62-b58c-11e6-ace0-b8a720524153]]@17875087
> targetConnector=ServerLocatorImpl [initialConnectors=[
> TransportConfiguration(name=netty-connector, factory=org-apache-activemq-
> artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61616&host=localhost], discoveryGroupConfiguration=
> null]]::ClusterConnectionImpl@1297836716[nodeUUID=63157c62-b58c-11e6-ace0-b8a720524153,
> connector=TransportConfiguration(name=netty-connector,
> factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61617&host=localhost, address=jms, server=ActiveMQServerImpl::
> serverUUID=63157c62-b58c-11e6-ace0-b8a720524153])) [initialConnectors=[
> TransportConfiguration(name=netty-connector, factory=org-apache-activemq-
> artemis-core-remoting-impl-netty-NettyConnectorFactory)
> ?port=61616&host=localhost], discoveryGroupConfiguration=null]] is
> connected
> 19:02:06,274 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-data-2.amq id = 2, recordID
> = 2) (size=10,485,760) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server1\data\server0\data\messaging\journal\activemq-data-2.amq
>
> 19:02:06,651 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-bindings-4.bindings id = 1,
> recordID = 1) (size=1,048,576) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server1\data\server0\data\messaging\
> bindings\activemq-bindings-4.bindings
> 19:02:06,659 INFO  [org.apache.activemq.artemis.core.server] AMQ221025:
> Replication: sending JournalFileImpl: (activemq-bindings-2.bindings id = 2,
> recordID = 2) (size=1,048,576) to backup. NIOSequentialFile
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server1\data\server0\data\messaging\
> bindings\activemq-bindings-2.bindings
> 19:02:07,046 INFO  [org.apache.activemq.artemis.core.server] AMQ221000:
> backup Message Broker is starting with configuration Broker Configuration
> (clustered=true,journalDirectory=C:\dev_temp\
> apache-artemis-1.5.0\examples\features\ha\mark-poc\target\
> server1\data/server0/data/messaging/journalcolocated_
> backup_01,bindingsDirectory=C:\dev_temp\apache-artemis-1.5.
> 0\examples\features\ha\mark-poc\target\server1\data/
> server0/data/messaging/bindingscolocated_backup_01,
> largeMessagesDirectory=C:\dev_temp\apache-artemis-1.5.0\
> examples\features\ha\mark-poc\target\server1\data/server0/data/messaging/
> largemessagescolocated_backup_01,pagingDirectory=C:\dev_
> temp\apache-artemis-1.5.0\examples\features\ha\mark-poc\
> target\server1\data/server0/data/messaging/pagingcolocated_backup_01)
> 19:02:07,054 INFO  [org.apache.activemq.artemis.core.server] AMQ221049:
> Activating Replica for node: 60b03b78-b58c-11e6-937d-b8a720524153
> 19:02:07,056 INFO  [org.apache.activemq.artemis.core.server] AMQ222162:
> Moving data directory C:\dev_temp\apache-artemis-1.
> 5.0\examples\features\ha\mark-poc\target\server1\data\
> server0\data\messaging\journalcolocated_backup_01 to
> C:\dev_temp\apache-artemis-1.5.0\examples\features\ha\mark-
> poc\target\server1\data\server0\data\messaging\journalcolocated_backup_01\oldreplica.1
>
> 19:02:07,059 INFO  [org.apache.activemq.artemis.core.server] AMQ221013:
> Using NIO Journal
> 19:02:07,059 WARN  [org.apache.activemq.artemis.core.server] AMQ222007:
> Security risk! Apache ActiveMQ Artemis is running with the default cluster
> admin user and default password. Please see the cluster chapter in the
> ActiveMQ Artemis User Guide for instructions on how to change this.
> 19:02:07,060 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 19:02:07,061 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-amqp-protocol]. Adding protocol support
> for: AMQP
> 19:02:07,063 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-hornetq-protocol]. Adding protocol support
> for: HORNETQ
> 19:02:07,064 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-mqtt-protocol]. Adding protocol support
> for: MQTT
> 19:02:07,065 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-openwire-protocol]. Adding protocol support
> for: OPENWIRE
> 19:02:07,066 INFO  [org.apache.activemq.artemis.core.server] AMQ221043:
> Protocol module found: [artemis-stomp-protocol]. Adding protocol support
> for: STOMP
> 19:02:07,076 INFO  [org.apache.activemq.artemis.core.server] AMQ221109:
> Apache ActiveMQ Artemis Backup Server version 1.5.0 [null] started, waiting
> live to fail before it gets active
> 19:02:08,015 INFO  [org.apache.activemq.artemis.core.server] AMQ221024:
> Backup server ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153
> is synchronized with live-server.
> 19:02:08,022 INFO  [org.apache.activemq.artemis.core.server] AMQ221031:
> backup announced
> 19:04:21,859 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.HBQueue in
> AddressSettings
> 19:04:21,859 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.HBQueue in AddressSettings
> 19:04:51,830 WARN  [org.apache.activemq.artemis.core.server] AMQ222092:
> Connection to the backup node failed, removing replication now:
> ActiveMQRemoteDisconnectException[errorType=REMOTE_DISCONNECT
> message=null]
>         at org.apache.activemq.artemis.core.remoting.server.impl.
> RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:533)
> [artemis-server-1.5.0.jar:1.5.0]
>         at org.apache.activemq.artemis.core.remoting.impl.netty.
> NettyAcceptor$Listener.connectionDestroyed(NettyAcceptor.java:681)
> [artemis-server-1.5.0.jar:1.5.0]
>         at org.apache.activemq.artemis.core.remoting.impl.netty.
> ActiveMQChannelHandler.channelInactive(ActiveMQChannelHandler.java:75)
> [artemis-core-client-1.5.0.jar:1.5.0]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:255)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:241)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> fireChannelInactive(AbstractChannelHandlerContext.java:234)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:360)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:325)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:255)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:241)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> fireChannelInactive(AbstractChannelHandlerContext.java:234)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.DefaultChannelPipeline$
> HeadContext.channelInactive(DefaultChannelPipeline.java:1329)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:255)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannelHandlerContext.
> invokeChannelInactive(AbstractChannelHandlerContext.java:241)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(
> DefaultChannelPipeline.java:908) [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:744)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(
> AbstractEventExecutor.java:163) [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(
> SingleThreadEventExecutor.java:418) [netty-all-4.1.5.Final.jar:4.1.5.Final]
>
>         at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440)
> [netty-all-4.1.5.Final.jar:4.1.5.Final]
>         at io.netty.util.concurrent.SingleThreadEventExecutor$5.
> run(SingleThreadEventExecutor.java:873) [netty-all-4.1.5.Final.jar:4.1.5.Final]
>
>         at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_74]
> 19:04:51,873 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,882 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,883 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:51,885 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,954 WARN  [org.apache.activemq.artemis.core.server] AMQ222095:
> Connection failed with failedOver=false
> 19:04:51,961 INFO  [org.apache.activemq.artemis.core.server] AMQ221029:
> stopped bridge sf.my-cluster.60b03b78-b58c-11e6-937d-b8a720524153
> 19:04:51,982 INFO  [org.apache.activemq.artemis.core.server] AMQ221037:
> ActiveMQServerImpl::serverUUID=60b03b78-b58c-11e6-937d-b8a720524153 to
> become 'live'
> 19:04:51,983 WARN  [org.apache.activemq.artemis.core.client] AMQ212037:
> Connection failure has been detected: AMQ119015: The connection was
> disconnected because of server shutdown [code=DISCONNECTED]
> 19:04:52,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:04:52,031 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue jms.queue.exampleQueue in
> AddressSettings
> 19:04:52,034 WARN  [org.apache.activemq.artemis.core.server] AMQ222165:
> No Dead Letter Address configured for queue sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:04:52,035 WARN  [org.apache.activemq.artemis.core.server] AMQ222166:
> No Expiry Address configured for queue sf.my-cluster.63157c62-b58c-11e6-ace0-b8a720524153
> in AddressSettings
> 19:04:52,127 INFO  [org.apache.activemq.artemis.core.server] Scaled down
> 0 messages total.
>
> ===========
> borker.xml:
> ===========
> <?xml version='1.0'?>
> <configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>                xmlns="urn:activemq"
>                xsi:schemaLocation="urn:activemq
> /schema/artemis-server.xsd">
>
>     <jms xmlns="urn:activemq:jms">
>
>         <queue name="exampleQueue"/>
>     </jms>
>
>     <core xmlns="urn:activemq:core">
>
>         <bindings-directory>${data.dir}/server0/data/messaging/
> bindings</bindings-directory>
>
>         <journal-directory>${data.dir}/server0/data/messaging/
> journal</journal-directory>
>
>         <large-messages-directory>${data.dir}/server0/data/
> messaging/largemessages</large-messages-directory>
>
>         <paging-directory>${data.dir}/server0/data/messaging/paging<
> /paging-directory>
>
>
>         <connectors>
>             <connector name="invm-connector">vm://0</connector>
>             <connector name="netty-connector">tcp://
> localhost:61616</connector>
>
>             <connector name="server1-connector">tcp:/
> /localhost:61617</connector>
>         </connectors>
>
>
>         <acceptors>
>             <acceptor name="invm-acceptor">vm://0</acceptor>
>             <acceptor name="netty-acceptor">tcp://
> localhost:61616</acceptor>
>         </acceptors>
>
>
>         <ha-policy>
>             <replication>
>                 <colocated>
>                     <max-backups>2</max-backups>
>                     <request-backup>true</request-backup>
>                     <backup-request-retry-interval>1000</backup-request-
> retry-interval>
>                     <excludes>
>                         <connector-ref>invm-connector</connector-ref>
>                         <connector-ref>server1-connector</connector-ref>
>                         <connector-ref>netty-connector</connector-ref>
>                     </excludes>
>                     <master/>
>                     <slave>
>                         <scale-down>
>                             <connectors>
>                                 <connector-ref>invm-connector<
> /connector-ref>
>                             </connectors>
>                         </scale-down>
>                     </slave>
>                 </colocated>
>             </replication>
>         </ha-policy>
>
>         <cluster-connections>
>             <cluster-connection name="my-cluster">
>                 <address>jms</address>
>                 <connector-ref>netty-connector</connector-ref>
>                 <retry-interval>500</retry-interval>
>                 <use-duplicate-detection>true</use-duplicate-detection>
>                 <message-load-balancing>OFF</message-load-balancing>
>                 <max-hops>1</max-hops>
>                 <static-connectors>
>                     <connector-ref>server1-connector</connector-ref>
>                 </static-connectors>
>             </cluster-connection>
>         </cluster-connections>
>
>
>
>         <security-settings>
>
>             <security-setting match="#">
>                 <permission type="createDurableQueue" roles="guest"/>
>                 <permission type="deleteDurableQueue" roles="guest"/>
>                 <permission type="createNonDurableQueue" roles="guest"/>
>                 <permission type="deleteNonDurableQueue" roles="guest"/>
>                 <permission type="consume" roles="guest"/>
>                 <permission type="send" roles="guest"/>
>                 <permission type="manage" roles="guest"/>
>             </security-setting>
>         </security-settings>
>
>     </core>
> </configuration>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/H-A-colocated-
> replication-environment-not-working-as-expected-tp4719539.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h35@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YW5keS50YXlsczY3QGdtYWlsLmNvbXwyMzQxODA1fC05MDE1NDk1MzM=>
> .
> NAML
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-environment-not-working-as-expected-tp4719539p4719540.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.