You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by khandelwalanuj <kh...@gmail.com> on 2014/02/02 12:08:08 UTC

Re: Current Connection Count for ActiveMQ broker

Thanks for the suggestions.
I cannot go ahead with the other approaches you specified because of some
reasons. 

So I just want to ask one more thing: 
If I am using plugin to get all the stats.
than is there any other way to get stats without creating
"*ManagementContext*" and "*BrokerViewMBean*". I meant to say some direct
APIs to get all the stats with creating BrokerViewMbeans ? 

And as you have specified :\
>> "It's not a heavy load on the broker unless it's being called rapidly."
How rapid you mean here. I am running this per minute. Will per minute
calling will be load on the broker ?


Thanks,
Anuj



--
View this message in context: http://activemq.2283324.n4.nabble.com/Current-Connection-Count-for-ActiveMQ-broker-tp4676635p4677278.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Current Connection Count for ActiveMQ broker

Posted by artnaseef <ar...@artnaseef.com>.
Ah, looking at the precise method of accessing the Admin View more carefully,
I recommend using BrokerService.getAdminView().

As for performance, I think once per minute is fine.  However, I recommend
measuring as there are many variables that play in.  I would try increasing
the rate (i.e. decrease the delay) until performance is notably impacted,
and then back off from there.  From there, a great picture of the
performance impact and reasonable rates is known.




--
View this message in context: http://activemq.2283324.n4.nabble.com/Current-Connection-Count-for-ActiveMQ-broker-tp4676635p4677281.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.