You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by GitBox <gi...@apache.org> on 2019/01/29 10:23:05 UTC
[GitHub] onlyMIT opened a new pull request #2528: ARTEMIS-2226 last consumer connection should close the previous consu…
onlyMIT opened a new pull request #2528: ARTEMIS-2226 last consumer connection should close the previous consu…
URL: https://github.com/apache/activemq-artemis/pull/2528
If use MQTT protocol, multiple consumers using the same clientId in the cluster, the last consumer connection should close the previous consumer connection!
There are two solutions to this issue:
> 1. Add a new cluster notification when the client’s connections connect to Artemis, close existing connections that use the same clientId when processing cluster-notification. This solution is the best way to address the MQTT agreement.But I don't think it's necessary to solve this problem by sending a cluster-notification every time client connect.
> 2.The solution is this RP used, close existing connections that use the same clientId when processing the CONSUMER_CREATE cluster-notification. No additional cluster-notification added. Only when a consumer using the same clientId consumes the same topic will it trigger a close connection.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services