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

Solution Unverified - Updated -

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]

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.