[ 
https://issues.apache.org/jira/browse/AMQ-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ysliu updated AMQ-5330:
-----------------------

    Description: I used a mqtt client, Paho, connected to ActiveMQ5.9.0 and 
subscribed a topic with cleansession=false. Then I found a durable consumer was 
created on specified topic. Then I unsubscribed from that topic and closed the 
mqtt connection. After that I found the durable consumer was still there. I 
think the durable consumer should be removed when client unsubscribed from the 
specified topic, otherwise the client would have no chance to remove it.  (was: 
I used a mqtt client, Paho, connected to ActiveMQ5.9.0 and subscribed a topic 
with cleansession=false. Then I found a durable consumer was created on 
specified topic. Then I unsubscribed from that topic and closed the mqtt 
client. After that I found the durable consumer was still there. I think the 
durable consumer should be removed when client unsubscribed from the specified 
topic, otherwise the client would have no chance to remove it.)

> MQTT unsubscribe command doesn't remove durable subscriber from topic
> ---------------------------------------------------------------------
>
>                 Key: AMQ-5330
>                 URL: https://issues.apache.org/jira/browse/AMQ-5330
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.9.0
>         Environment: windows xp sp3
>            Reporter: ysliu
>
> I used a mqtt client, Paho, connected to ActiveMQ5.9.0 and subscribed a topic 
> with cleansession=false. Then I found a durable consumer was created on 
> specified topic. Then I unsubscribed from that topic and closed the mqtt 
> connection. After that I found the durable consumer was still there. I think 
> the durable consumer should be removed when client unsubscribed from the 
> specified topic, otherwise the client would have no chance to remove it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to