activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2666) JMX does not indicate durable subscription activity.
Date Fri, 05 Aug 2011 15:39:27 GMT

     [ 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

        

Mime
View raw message