ActiveMQ MQTT: Duplicate Client ID behavior

Solution In Progress - Updated -

Issue

According to the MQTT specifications, during the CONNECT phase, a Server mud do the following:

If validation is successful the Server MUST perform the following steps.
1. If the ClientId represents a Client already connected to the Server then the Server MUST disconnect the existing Client [MQTT-3.1.4-2].

In the current JBoss A-MQ, when connecting a second client with the conflicting client id, the broker currently blocks the second connection instead of following the behavior described in the specification.

Is this a bug that you plan to fix?

Environment

  • JBoss A-MQ 6.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.