activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Buchi Reddy B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3802) Successful unsubscribing should not report inactive durable topic subscribers
Date Mon, 07 May 2012 07:50:07 GMT

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

Buchi Reddy B commented on AMQ-3802:
------------------------------------

Okay. It works finally with the following code though without using client-id while unsubscribing.

{quote}
$stomp->unsubscribe({destination => '/topic/test_topic'});
$stomp->unsubscribe({destination => '/topic/test_topic', 'activemq.subscriptionName'
=> 'test_subscription'});
{quote}

@Timothy I find this design a little weird. Do we have any reasons on why the design is like
this?
Also, I see that this works only if client-id given while subscribing is same as the subscription
name. I do not see any legitimate reason for doing that also. Can you please give us some
background details for this? Or share some wiki page which throws more light on this please.

FWIW, I feel that we should merge those two unsubscribe calls into one, to make best client
side design for this case. Can you give your opinion on that?
                
> 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

        

Mime
View raw message