JDK-4244774 : ThreadGroup.uncaughtException isn't sufficient
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.1.6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 1999-06-08
  • Updated: 2000-09-08
  • Resolved: 2000-09-08
Related Reports
Duplicate :  
JDK-4063022 - RFE: Awt ThreadGroup catches all UncaughtExceptions
Description

Name: vi73552			Date: 06/08/99


ThreadGroup.uncaughtException is ok if the user creates a Thread & chooses which ThreadGroup to put it in, but what about GUI threads & their ThreadGroups?  It's my understanding that I can't control anything about those threads or their groups, so I have no way to override the default behavior of uncaughtException.

One alternative might be to define an interface for handling uncaught exceptions & make the current handler a property of ThreadGroup that can be get & set.  (I presume that access to setHandler would be checked.)
(Review ID: 84071) 
======================================================================
Comments
EVALUATION I suspect that the GUI framework should provide a way to do this. In general, it may not be appropriate for internal threads of a framework or service to be open to this kind of manipulation from the outside, so a general mechanism implemented at the level of the Thread class would not be the best solution. william.maddox@Eng 1999-12-17 Sounds like a duplicate of 4063022. eric.hawkes@eng 2000-09-08
17-12-1999