Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 2 May 2012 05:49:12 +0000 (UTC)
From: "Buchi Reddy B (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1951474742.16059.1335937752192.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <461178188.16804.1333630284021.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3802) Successful unsubscribing should not
 report inactive durable topic subscribers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Buchi Reddy B commented on AMQ-3802:
------------------------------------

@Timothy

As I have mentioned already, I have tried to give the 'activemq.subscriptionName' in the unsubscribe call as well but still seeing this issue.

Can you please try this problem with this code?

    use Net::Stomp;

    my $stomp = Net::Stomp->new( { hostname => 'mybroker', port => '61613' } );

    $stomp->connect( { client-id => 'test_client', login => '', passcode => ''} );
    print "connected \n";

    $stomp->subscribe({ destination => '/topic/test_topic', 'activemq.subscriptionName' => "test_subscription" });
    print "subscribed \n";

    sleep(3);
    $stomp->unsubscribe({destination => '/topic/test_topic', 'activemq.subscriptionName' => "test_subscription"});

    sleep(2);
    $stomp->disconnect;

And, to give more details to you, in Jconsole of the broker, I clearly see that the subscription is shown as test_subscription under the Durable topics before the client sends unsubscribe and is being shown under "false" topics with the following name after the client unsubscribes.
ID_infraprod1.hyd.deshaw.com-34343-1335687381802-2_13_test_subscription

Does this give any clue?

                
> Successful unsubscribing should not report inactive durable topic subscribers
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-3802
>                 URL: https://issues.apache.org/jira/browse/AMQ-3802
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Solaris,Linux
>            Reporter: Bhanu
>
> An unsubscribe call should remove the client from inactive durable topic subscribers list. In the current broker behavior, even if a durable consumer unsubscribes & shuts down gracefully, the broker marks the durable subscriber as inactive. If this durable subscriber was never meant to come up again(as in my case where i am testing rigorously using unique client-ids each time based on pid) then broker will unnecessarily mark a lot of consumers as inactive durable.
> For inactive durable subscribers, there is no distinction between a subscriber going down abruptly or unsubscribing & going down gracefully.
> This should be improved I think. Moreover, any tips on how to remove those 1000s of inactive subscriptions dangling in my Jconsole ?? Destroying each manually isn't an option !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira