We can now have JMX control over the backend, from the command line,
using ovirt authentication 
It's is now very easy to:
1. raise logging level to DEBUG
2. get threading info
3. get transaction stats
4. interact with whatever we exposed as JMX beans (like LockManager)
5. shutdown, redeploy context and so on...
--controller=127.0.0.1:8706 --connect --user=admin@internal \
See more examples in the commit message.
Currently only admin@internal would be allow to perform such actions. We
may consider to extend that to a dedicated system role.
(included in version 3.6)