You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/08/05 17:39:27 UTC
[jira] [Closed] (AMQ-2666) JMX does not indicate durable
subscription activity.
[ https://issues.apache.org/jira/browse/AMQ-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-2666.
-----------------------------
Resolution: Not A Problem
Working as designed.
> JMX does not indicate durable subscription activity.
> ----------------------------------------------------
>
> Key: AMQ-2666
> URL: https://issues.apache.org/jira/browse/AMQ-2666
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: Akos Baraz
> Fix For: 5.6.0
>
> Attachments: DurableSubscriptionReactivationTest3.java, activemq2.xml
>
>
> The ManagedRegionBroker.addInactiveSubscription adds the subscription to this domain: "...Type=Subscription,active=false,name=...". I don't know what this active=false part supposed to mean, but it puts the MBean to a strange path in the jconsole. What is not a big problem, but it is not managed by the rest of the code. Even if a subscription is inactivated the MBean in the "Durable" section shows active. If the subscription is active the "false" section contains an entry as it would be inactive.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira