No real standard available, but HermesJMS is commonly used. More info here:

http://www.hermesjms.com/

http://blog.swesource.com/2012/08/hermesjms-setup-for-hornetq.html

HornetQ exposes it's management interface via JMX so any GUI tool that can work with MBeans can be used to manage HornetQ.  I suppose JConsole would be the "standard" GUI since it ships with Java.

While Hermes is a useful tool, as I understand it, it only uses JMS.  In other words, it doesn't use JMX hence it can't leverage all the HornetQ management MBeans.  At best it is a partial solution to HornetQ management.

I don't see any configuration options related to JMX on the "Screenshots" tab at http://www.hermesjms.com/confluence/display/HJMS/HornetQ.  The only URL I see in there is for JNDI (i.e. "jnp://localhost:1099") which is what Hermes will use to lookup connection factories and destinations.  It won't use that URL to access the HornetQ MBeans via JMX.

On the "Plugin" tab I see something related to JMX.  It says:

The plugin lets you get queue and durable subscription depth as well as to truncate queues and durable subscriptions. It does not natively browse a durable subscription.

 

You must set the jmxUrl property to something like service:jmx:rmi:///jndi/rmi://localhost:1090/jmxconnector

Apparently the only functionality here provided via JMX is getting the queue and durable subscription depth and deleting messages and durable subscriptions.  However, the HornetQ management interface exposed via JMX is much richer than just these few functions, and it certainly doesn't appear that you can access it all via Hermes.