Clustered JBoss A-MQ produces "Failed to add Connection ID:xx" warnings

Solution Verified - Updated -

Issue

  • When my second JBoss A-MQ broker starts, the following WARN messages are logged in the log file repeatedly:
WARN  (ActiveMQ VMTransport: vm://amq01-broker#5-1) [org.apache.activemq.broker.TransportConnection] 104-org.apache.activemq.activemq-osgi:5.8.0.redhat-60024 | Failed to add Connection ID:<connection_id>:1, reason: javax.jms.InvalidClientIDException: Broker: amq01-broker - Client: NC_amq02-broker_inbound_amq01-broker already connected from vm://amq01-broker#0

Environment

  • Red Hat JBoss A-MQ
    • 6.0
  • a cluster of two JBoss A-MQ brokers

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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