David Herron's Blog

A useful testing technique to find deadlocks related to invokeAndWait

Tom Hawtin writes about a deadlock he found in jedit 4.2. As he says: There was, however, a use of invokeAndWait. Sure enough the EDT was waiting on monitor locked by the thread calling invokeAndWait.

What's most interesting is a class he provides to help one automatically find those situations. It relies on a Mustang ability provided through the JMX support to query all held locks. The code looks to see if the Event Dispatch Thread is called with a parent stack frame in invokeAndWait, and then checks the locks. Really cool.

Comments

• See also "Automatically detecting AWT event dispatch thread hangs"
  

  Posted by: coxcu on January 30, 2006 at 03:30 PM

This work is licensed under a Creative Commons License.