ActiveMQ Broker getting javax.jms.InvalidClientIDException

Solution Unverified - Updated -

Issue

  • 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:///192.168.156.101:4098@61616 | TransportConnection      | emq.broker.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://192.168.156.101:4076

Environment

  • Fuse Message Broker 5.x
  • ActiveMQ 5.5.1

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.