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 Fri, 11 May 2012 12:41:50 GMT


Buchi Reddy B commented on AMQ-3802:

There seems to be another issue if a single client has multiple durable subscriptions. If
the client-id and subscriptionName should be same for a durable subscription, how can the
same client subscribe to a second durable namespace? I have tried this and saw that broker
sends error message indicating there is a durable subscriber already with the same client-id
and subscriptionName.

Can you please suggest us how to fix this?
> 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