All these informations are available using JMX and a JMX console (e.g. jconsole).
Have a look at the management chapter in the user manual and the management API javadoc.
One of the reasons, our OPS team is hesistant to adopt/embrace JBoss-AS is its lack of good admin/management tool.
I knwo JMX console is good but do you really expect the OPS to fumble through the jmx-console to do some operations.
For JBOSS-AS: JON is trying to fill in the gap, wondering about HornetQ.
Personally, I feel: HornetQ may be a awsome JMS Server but you can its widescale adoption if you don't have good/easy tools to manage/administer it. It may very well be hermeez or something else...
I am really excited about this and hoping I have some way to manage/administer this.
This is already on the road-map.
There is a JIRA task for 2.1 for integrating with JON. (See JIRA)
I would wait for GA to be out and we may be one of the biggest deployments of HornetQ if things go well.
Sometime next year, I may be taking HornetQ in our lab to test this out, right now, I am just keeping an eye over it.