I didn't see a specific description of the protocol between the broker and the agent, but I assume it's qpid, which means hornetq running on the agent???
Based on our discussion in Madison, we don't want complex subsystems like HQ running on the domain controller. We'd discussed having it run the native Java protocol and a simple http server for REST. However, we decided to provide a separate server profile intended to run the domain management webapp. Perhaps a hornetq-based QMF agent could be added to that profile?
I know the JON folks prefer a metadata based management API instead of coding directly to a complex set of classes. So if we're going to develop the metadata and we're eventually going to have to support QMF's, we should consider just using it now.
TBH though, this doesn't look really fleshed out to me, and they are apparently looking at changing the protocol:
https://cwiki.apache.org/qpid/qmf-map-message-protocol.html
Trying to target something that is unstable makes me very nervous.