JDK-6214784 : REGRESSION:TraceMsgQueueChecker is written unsafely
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 5.0,5.0u1,6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2005-01-06
  • Updated: 2010-12-06
  • Resolved: 2005-01-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
5.0u2Fixed 6 b20Fixed
Related Reports
Duplicate :  
Description
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.

http://www.javadesktop.org/forums/thread.jspa?messageID=48188%EB%B0%BC
###@###.### 2005-1-06 19:04:08 GMT

Comments
SUGGESTED FIX set the TraceMsgQueueChecker thread to a daemon thread: http://web-east.east/deployment/www/webrevs/ngthomas/6214784/webrev/ ###@###.### 2005-1-07 00:27:46 GMT
07-01-2005

EVALUATION this is actually a regression from 1.4.2, we should fix it in a tiger update release too. ###@###.### 2005-1-07 00:27:46 GMT ###@###.### 2005-1-07 00:28:00 GMT
07-01-2005