TraceMsgQueueChecker is written unsafely - it doesn't check for
interrupted state and rolls in the infinite unconditional loop
Comments from Swing team: It use to be the case that starting up the AWT thread would force you to have to call System.exit, but that is no longer the case. If all the AWT heavy weights (like JFrame) have been properly disposed and there are no events on the event queue than the AWT event queue will exit allowing the app to exit without invoking System.exit. There must be a non-daemon thread started by Webstart that is preventing the App from exiting when all other threads have exited. Or it could be non-disposed heavy weights.
###@###.### 2005-1-06 19:04:08 GMT