Related to issue #132 (but seems diff enough because it should probably always be on, instead of just being an option).

If a deadlock can be detected (via ThreadMXBean.html.findDeadlockedThreads()) when the HEARTBEAT messages are being reported, it would be good to included at least the bare details in the HEARTBEAT log message (ie: "...DEADLOCKED!")

Since a deadlock may be temporary (Lock.tryLock with a really long delay for example) it shouldn't automatically kill the test -- but maybe that should be an option?

I started to try and come up with a patch for this, but then realized i had no idea how to get the JMX info from the slave process so that the master thread could get the ThreadMXBean (but this seems like a general problem blocking #132 as well -- how to get the thread/stack info remotely from the slave JVM)