JDK-4162893 : Threads should exit gracefully when interrupted
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1998-08-03
  • Updated: 1999-01-15
  • Resolved: 1999-01-15
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
1.2.0 1.2fcsFixed
Related Reports
Relates :  
JDK-4159054 - sun.awt.AppContext needs a dispose()
Description
Now that AppContext has a dispose() method which interrupts threads and
waits for them to exit, all per-AppContext AWT threads should exit gracefully
when interrupted.  Thus, their event-dispatching loops should check
isInterrupted() and the InterruptedException from wait() should cause the
run() method to return.

This applies to the EventDispatchThread, PostEventQueue, and appletviewer
event handler threads.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2fcs INTEGRATED IN: 1.2fcs
14-06-2004
EVALUATION Updated the EventDispatchThread, PostEventQueue, and appletviewer threads to exit gracefully when InterruptedException is caught or isInterrupted() returns true. Also changed appletviewer's AppletPanel.sendEvent() to not hold the queue locked while calling AppContext.dispose(), which was causing appletviewer's event handler thread to not exit gracefully. fred.ecks@Eng 1998-08-03
03-08-1998