Maybe a better approach would be to start a Jetty with JMX enabled, so
you can use JConsole to manage it?
If you take this route, however, note that much better approach is to
get Jetty bean by type (not name).
I guess the ActiveMQ OSGi architecture would tackle this nicely?
Cheers
--
Dejan Bo
It is using xbean config to start broker and jetty etc.
currently BrokerService jmx stop will stop the broker but embeded jetty
server will keep running so the java process does not quit without a Ctrl+C.
and activemq-admin stop has the same effect also activemq-admin stop simply
calls terminateJ
