Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 11 May 2012 12:45:51 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1882861980.54169.1336740351859.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=13273212#comment-13273212 ] 

Timothy Bish commented on AMQ-3802:
-----------------------------------

Can you post a sample of you stomp client subscribing to two durables?
                
> 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