ActiveMQ Broker getting javax.jms.InvalidClientIDException

Solution Unverified - Updated -


  • Starting up multiple brokers using a networkConnector to a central broker causes a javax.jms.InvalidClientIDException to be output in the central broker's log.

  • We are getting these warning messages in our logs:

WARN  | ActiveMQ Transport: tcp:/// | TransportConnection      |  705 | Failed to add Connection ID:UK003408-1084-1385645810303-2:148, reason: javax.jms.InvalidClientIDException: Broker: my_activemq - Client: eReSFS_UK003408 already connected from tcp://


  • Fuse Message Broker 5.x
  • ActiveMQ 5.5.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content