JDK-4277909 : When a java application crashes on windows, dump the thread stacks to a log
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.0
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_95
  • CPU: x86
  • Submitted: 1999-10-04
  • Updated: 2000-02-03
  • Resolved: 2000-02-03
Related Reports
Duplicate :  
JDK-4287415 - Reliability and Availability Improvements
Description

Name: skT88420			Date: 10/04/99


On AIX, when the JVM crashes, the thread stack traces are
written to a log in the same directory as the java executable.
This is really useful in figuring out what triggered the
crash, and I think it would help JavaSoft in debugging
JVM crashes on windows, especially as windows continues to
evolve.

Also nice to have would be a way to send a hung java application
a signal to dump the thread stack.  AIX also provides this
with the "kill" command.  I know I can type ctrl-break in
the console that launched Java, however, this doesn't help
if you are using javaw.exe in your release version.
(Review ID: 96088) 
======================================================================
Comments
EVALUATION The output of the hotspot VM can be redirected by supplying an jio_vfsnprintf functiom to the VM. This will require a specialized launcher, but is possible. See the invocation API for details rene.schmidt@eng 1999-10-28 I'm reopening this as a low-priority RFE. We are interested in making it easy to diagnose failures, especially in high availability server environments where it may not be possible to interactively debug. david.stoutamire@Eng 1999-10-29 This issue is subsumed by the Merlin availability features. Closing as a duplicate of the bugtraq entry being used for that. david.stoutamire@Eng 2000-02-03
29-10-1999