Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 3 May 2012 05:34:02 +0000 (UTC)
From: "Bhanu (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <482597546.20571.1336023242571.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <461178188.16804.1333630284021.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3802) Successful unsubscribing should not
 report inactive durable topic subscribers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267206#comment-13267206 ] 

Bhanu commented on AMQ-3802:
----------------------------

Tim,

I was playing around with Buchi's test, made some pretty minor changes and I am getting the below exception that durable consumer is in use ! 


2012-05-03 10:59:21,204 | INFO  | Removing subscription : RemoveSubscriptionInfo {commandId = 4, responseRequired = false, connectionId = ID:desh0007.hyd.desh
aw.com-59732-1336021109112-3:8, clientId = test, subscriptionName = test} | org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport: tcp:///1
0.240.170.27:42262
2012-05-03 10:59:21,205 | WARN  | Async error occurred: javax.jms.JMSException: Durable consumer is in use | org.apache.activemq.broker.TransportConnection.S
ervice | ActiveMQ Transport: tcp:///10.240.170.27:42262
javax.jms.JMSException: Durable consumer is in use
        at org.apache.activemq.broker.region.TopicRegion.removeSubscription(TopicRegion.java:138)
        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.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.BrokerFilter.removeSubscription(BrokerFilter.java:101)
        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)
2012-05-03 10:59:21,205 | WARN  | Exception occurred processing:
null: javax.jms.JMSException: Durable consumer is in use | org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ Connection Dispatcher: /10.240.170.27:42262

Any clues !?

                
> 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