[
https://issues.apache.org/jira/browse/AMQ-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266501#comment-13266501
]
Buchi Reddy B commented on AMQ-3802:
------------------------------------
@Timothy,
I have changed the code to give same id on client-id and
'activemq.subscriptionName' but still helpless.
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.
{quote}
2012-05-02 17:28:14,299 | INFO | Removing subscription :
RemoveSubscriptionInfo {commandId = 4, responseRequired = false, connec
tionId = ID:invest8.hyd.deshaw.com-48938-1335959820654-2:2, clientId =
test_subscription, subscriptionName = test_subscription} |
org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
tcp:///149.77.160.37:63026
2012-05-02 17:28:14,304 | DEBUG | Error occured while processing async command:
RemoveSubscriptionInfo {commandId = 4, responseRequired = false, connectionId =
ID:invest8.hyd.deshaw.com-48938-1335959820654-2:2, clientId =
test_subscription, subscriptionName = test_subscription}, exception:
javax.jms.InvalidDestinationException: No durable subscription exists for:
test_subscription | org.apache.activemq.broker.TransportConnection.Service |
ActiveMQ Transport: tcp:///149.77.160.37:63026
javax.jms.InvalidDestinationException: No durable subscription exists for:
test_subscription
at
org.apache.activemq.broker.region.TopicRegion.removeSubscription(TopicRegion.java:135)
at
org.apache.activemq.broker.region.RegionBroker.removeSubscription(RegionBroker.java:491)
at
org.apache.activemq.broker.BrokerFilter.removeSubscription(BrokerFilter.java:101)
at
org.apache.activemq.broker.BrokerFilter.removeSubscription(BrokerFilter.java:101)
at
org.apache.activemq.broker.BrokerFilter.removeSubscription(BrokerFilter.java:101)
at
org.apache.activemq.broker.BrokerFilter.removeSubscription(BrokerFilter.java:101)
at
org.apache.activemq.broker.MutableBrokerFilter.removeSubscription(MutableBrokerFilter.java:107)
at
org.apache.activemq.broker.util.LoggingBrokerPlugin.removeSubscription(LoggingBrokerPlugin.java:211)
at
org.apache.activemq.broker.MutableBrokerFilter.removeSubscription(MutableBrokerFilter.java:107)
at
org.apache.activemq.broker.TransportConnection.processRemoveSubscription(TransportConnection.java:342)
at
org.apache.activemq.command.RemoveSubscriptionInfo.visit(RemoveSubscriptionInfo.java:81)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:306)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:81)
at
org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:140)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:456)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommand(ProtocolConverter.java:190)
at
org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:70)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:220)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202)
at java.lang.Thread.run(Thread.java:722)
{quote}
> 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
