activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Buchi Reddy B (JIRA)" <>
Subject [jira] [Commented] (AMQ-3802) Successful unsubscribing should not report inactive durable topic subscribers
Date Wed, 02 May 2012 05:49:12 GMT


Buchi Reddy B commented on AMQ-3802:


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";

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


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.

Does this give any clue?

> Successful unsubscribing should not report inactive durable topic subscribers
> -----------------------------------------------------------------------------
>                 Key: AMQ-3802
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message