[
https://issues.apache.org/jira/browse/ARTEMIS-2226?focusedWorklogId=194622&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-194622
]
ASF GitHub Bot logged work on ARTEMIS-2226:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Feb/19 15:54
Start Date: 05/Feb/19 15:54
Worklog Time Spent: 10m
Work Description: onlyMIT commented on issue #2528: ARTEMIS-2226 last
consumer connection should close the previous consu…
URL: https://github.com/apache/activemq-artemis/pull/2528#issuecomment-460691058
@michaelandrepearce As described in my comment.Even if use a plugin, we
can't use notifications in the plugin like SESSION_CREATED，it can't achieve our
goal, modify the SESSION_CREATED filter? I think we need to think carefully,
and if we modify their filtering rules, we can't affect the existing logic. We
need to conduct comprehensive testing and evaluation.I think the plugin should
be where the optional code is placed, and the logic that is must required is
not suitable for the plugin.
Like the first version I submitted, the logic was placed in CONSUMER_CREATE,
the readability was too poor and not exactly matched with the MQTT
specification;
This version the logic was added by adding CONNECTED_CREATED. It seems that
not all protocols are used, and it is not the most Good plan.
If you want to use SESSION_CREATED, CONNECTION_CREATED, must force the
MQTT protocol to open all plugins? and modify the filter so that the
SESSION_CREATED notification can communicate between the clusters. This is the
risk of making the original notification rules undefined，and need to modify
their filtering rules, I am not sure if modifying the filtering rules will
introduce other issues.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 194622)
Time Spent: 18h 10m (was: 18h)
> (MQTT)In the cluster,the last consumer connection should close the previous
> consumer connection
> -----------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2226
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2226
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Shiping Liang
> Priority: Major
> Time Spent: 18h 10m
> Remaining Estimate: 0h
>
> Multiple consumers using the same clientId in the cluster, the last consumer
> connection should close the previous consumer connection!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
