Unexplained Behavior (warning and exception stack traces) on HornetQ fail-back

Issue

• We are testing JBoss EAP HornetQ fail over. The test environment consists of two EAP instances (ServerA and ServerB). Each EAP instance runs a set of two collocated HornetQ instances in a active/backup configuration. The HA uses in-memory replication - no shared file system. We only use the pair A in the failover experiments.

• If we kill ServerA and restart, the fail-back seems to occur fine, in that all messages can be read from the re-established active node. However, warnings and exception stack traces show up in the active node log:

WARN  [org.hornetq.core.client] (Thread-6 (HornetQ-client-global-threads-864296343)) HQ212028: error starting server locator: HornetQException[errorType=ILLEGAL_STATE message=null]
        at org.hornetq.core.client.impl.ServerLocatorImpl.initialise(ServerLocatorImpl.java:369) [hornetq-core-client-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]