JDK-4300827 : (spec thread) ThreadDeath should note that stop is @deprecated
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-12-21
  • Updated: 2007-06-22
  • Resolved: 2011-05-18
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.
JDK 7
7 b15Fixed
Related Reports
Relates :  
JDK-4189292 - (thread spec) ThreadGroup and Thread need better and tighter specs
Description
The only legitimate source of a ThreadDeath, java.lang.Thread.stop(), has
been deprecated.  For consistency and to avoid misleading developers,
java.lang.ThreadDeath should be deprecated, too.

I asked Josh (on 10/28/99), and he agrees.
Comments
EVALUATION Deprecation now is reserved for APIs which are considered dangerous to use. It is stop() that is (and should be) deprecated. Calling stop() is anti-social - defending against it should not be. It is reasonable in some cases to catch ThreadDeath, when well-behaved code has to interact with ill-mannered legacy code.
07-06-2007
SUGGESTED FIX http://javaweb/java/jdk/ws/libs/rev/4300827 This will need at least CCC.
08-05-2007
EVALUATION Worthwhile.
08-05-2007