[ 
https://issues.apache.org/jira/browse/ARTEMIS-2226?focusedWorklogId=194631&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-194631
 ]

ASF GitHub Bot logged work on ARTEMIS-2226:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Feb/19 16:00
            Start Date: 05/Feb/19 16:00
    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-460693569
 
 
   Now let's solve it step by step. First, we need to determine whether to use 
the existing notification or add a new notification to handle this logic. If I 
comment, it seems that the existing notification is not suitable.
   In the second step, if we use the new notification, we need to determine how 
to make it more reasonable.
   
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 194631)
    Time Spent: 18h 20m  (was: 18h 10m)

> (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 20m
>  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)

Reply via email to