Thanks for the clarification on the embedded broker question. A broker filter will do the job, as you described.
On the other hand, you could have written a tool that connects to the broker JVM via JMX and gets the counts that way, without putting custom code into the broker JVM. Such a tool can be handy for grabbing all kinds of broker statistics. As James mentions, using jconsole or visualvm (JMX clients), are great tools for a user to quickly and easily get the connection count from a broker. For automated logging, a good toolset here is OpenTSDB for metrics collection (where connection count is one metric) and jmxtrans to collect those statistics and push into OpenTSDB, which gives powerful reporting, such as graphs of metrics, and can be used with monitoring and alerting tools. Then it is possible to collect other stats of high importance with ActiveMQ, such as average enqueue times. Note that I would have to check if connection count specifically can easily be obtained with that toolset. If not, it should be a minor enhancement, to either jmxtrans or activemq, to obtain that stat. -- View this message in context: http://activemq.2283324.n4.nabble.com/Current-Connection-Count-for-ActiveMQ-broker-tp4676635p4676760.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
