[
https://issues.apache.org/jira/browse/AMQ-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253532#comment-13253532
]
Buchi Reddy B commented on AMQ-3802:
------------------------------------
This is easily reproducible with STOMP durable subscribers.
Please see the below code for example.
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'});
sleep(2);
$stomp->disconnect;
When I run this client, I clearly see that the broker shows the client in
inactive durable subscriptions list.
> 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
