Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 1 Apr 2014 01:27:16 +0000 (UTC)
From: "Netlancer (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12705519.1396155566869.40597.1396315636052@arcas>
In-Reply-To: <JIRA.12705519.1396155566869@arcas>
References: <JIRA.12705519.1396155566869@arcas>
Subject: [jira] [Commented] (AMQ-5127) MQTT Subscriber with QoS.EXACTLY_ONCE
 receives messages even after unsubscribing from topic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955984#comment-13955984 ] 

Netlancer commented on AMQ-5127:
--------------------------------

Hi Timothy Bish ,

 The test added reproduces the issue as it has assertEquals(10, received);. the subscriber should not receive those messages. This behaviour has been verified with mosquitto server. Please, let me know if my understanding is not correct. 

Thanks,
nl 

> MQTT Subscriber with QoS.EXACTLY_ONCE receives messages even after unsubscribing from topic
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-5127
>                 URL: https://issues.apache.org/jira/browse/AMQ-5127
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.9.0
>            Reporter: Netlancer
>              Labels: mqtt
>             Fix For: 5.10.0
>
>         Attachments: AMQ-5127.patch, MQTTTest.patch
>
>
> How to reproduce:
> 1. client c1 ( clientid1) connects, subscribes to topic A with QoS.EXACTLY_ONCE , unsubscribes topic A and disconnects.
> 2. client c2 ( clientid2) publishes to topic A with QoS.EXACTLY_ONCE.
> 3. client c1 ( clientid1) connects back again.
> Expectation : client c1 shouldn't receive any messages as it has already unsubscribed
> Attached test method to reproduce this issue


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