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 12:04:50 GMT


Buchi Reddy B commented on AMQ-3802:


I have changed the code to give same id on client-id and 'activemq.subscriptionName' but still

I tried running broker in DEBUG logging mode and I see the below log messages in broker when
I run this client. I am putting them if they can help you to debug this issue further.

2012-05-02 17:28:14,299 | INFO  | Removing subscription : RemoveSubscriptionInfo {commandId
= 4, responseRequired = false, connec
tionId =, clientId = test_subscription,
subscriptionName = test_subscription} | | ActiveMQ Transport: tcp:///
2012-05-02 17:28:14,304 | DEBUG | Error occured while processing async command: RemoveSubscriptionInfo
{commandId = 4, responseRequired = false, connectionId =,
clientId = test_subscription, subscriptionName = test_subscription}, exception: javax.jms.InvalidDestinationException:
No durable subscription exists for: test_subscription |
| ActiveMQ Transport: tcp:///
javax.jms.InvalidDestinationException: No durable subscription exists for: test_subscription
        at org.apache.activemq.command.RemoveSubscriptionInfo.visit(
        at org.apache.activemq.transport.TransportFilter.onCommand(
        at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(
        at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(
        at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(
        at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommand(
        at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(
        at org.apache.activemq.transport.TransportSupport.doConsume(
        at org.apache.activemq.transport.tcp.TcpTransport.doRun(

> 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