James.Strachan wrote:
>
>
> Thanks for the reply.
>
>> Strange. I was just looking at why we have DurableSubscriptionView and
>> InactiveDurableSubscriptionView; I don't understand why there are 2
>> classes for that. Surely being active/inactive is just a boolean flag
>> :)
>
> Agreed. Also I don't beleive the active=true/false should be in the
> ObjectName. Hermes has to construct the ObjectName dynamically from a
> topic name (for example to get pending messages depth) and should not
> have to worry about whether a consumer is active not - currently I try to
> see if the"inactive" MBean is there and if its not then I try to find the
> "active" MBean.
>
>> Does anyone know why there are 2 classes for the same thing? I'm
>> tempted to merge them.
>
> That gets my vote FWIW :)
>
>> However I don't see any more or less operations on either of these two
>> objects so don't quite follow why you see different operations?
>
> Try it with jconsole. Restart a broker that has a durable subscription.
> Look at the MBean and it will not have any operations available. Create a
> consumer for it and they appear.
>
> Finally, anyone got any thoughts on the lack of a queue MBean until the
> queue is used?
>
> Colin.
> http://hermesjms.com
>
>
>
>
>> It also seems that once connection clientID=XXX is established then all
>> Subscription MBeans become active=true even if there is only an active
>> consumer for one of them.
>
> That sounds like a JMX bug
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>
--
View this message in context:
http://www.nabble.com/ActiveMQ-JMX-Questions..-tf1917262.html#a5265442
Sent from the ActiveMQ - User forum at Nabble.com.
