Sure, that's true. Or if you're doing this in code, you could parse the
XML of your broker config file to determine that info and output it when
you log the destination.
But I think this would be a useful addition to the JMX MBean attributes;
why don't you submit an enhancement request? If you'r
What I mean is there is no indicator if I change defaults. All I can do is
remember all topics which I have configure as virtual along with their
consumer queue.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stats-for-Virtual-Topic-tp4690237p4690309.html
Sent from the A
Well, the default configuration for Virtual Topics (
http://activemq.apache.org/virtual-destinations.html) specifies that all
topics that are virtual begin with "VirtualTopic." and all consumer queues
for virtual topics begin with "Consumer.*.VirtualTopic.", and even if
you've changed the default c
In Jconsole, there is nothing which says anything about virtual destination.
It will all topics and queues as normal only. There is no distinguishing
factor.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stats-for-Virtual-Topic-tp4690237p4690287.html
Sent from the Activ
Have you looked at what's exposed in JMX (e.g. in JConsole)? Are those
things not available for virtual destinations? (I don't use them, so I
don't know.)
On Jan 22, 2015 6:55 AM, "bansalp" wrote:
> Stats like
> - List of topics which are virtual.
> - which all queue are consumer queue for each
Stats like
- List of topics which are virtual.
- which all queue are consumer queue for each virtual topic.
- Message size and count related stats for consumer queue.
- Any other stats that is exposed.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stats-for-Virtual-To
What kind of stats did you have in mind?
On Jan 22, 2015 12:15 AM, "bansalp" wrote:
> I have started using virtual topic in myActiveMQ setup and I was wondering
> if
> there are any stats available for virtual topic which I can log.
>
> --bansalp
>
>
>
> --
> View this message in context:
> http:
