|
Quick Lists
|
|
Bug ID:
|
5068433
|
|
Votes
|
0
|
|
Synopsis
|
(process) Thread dump on windows does not include child process'
|
|
Category
|
java:classes_lang
|
|
Reported Against
|
1.4.2_04
, merlin-ora
|
|
Release Fixed
|
|
|
State
|
6-Fix Understood,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4244515
,
4957071
|
|
Submit Date
|
25-JUN-2004
|
|
Description
|
After running many test with j2se 1.4.2_04 and j2se 1.5 beta on Solaris and Windows. Solaris DOES show the child process' threads in the stack dump for both j2se version. Windows DOES NOT for both j2se versions.
Windows only shows the parent process that is receiving the CTRL-BRK. When a child process is created using a Runtime exec, those threads are not including in the dump on windows.
For Solaris and Linux the thread dump shows all the threads for the parent and child processes.
xxxxx@xxxxx 2004-06-25
xxxxx@xxxxx 2004-06-25
|
|
Work Around
|
Use a process listing program to get the pid of the relevant child
process, and send the signal manually. I would try using, for example,
MKS ps and kill.
xxxxx@xxxxx 2004-06-26
|
|
Evaluation
|
DETACHED_PROCESS will be used less frequently if and when the changes for bug
5008166: (process) Various improvements to Windows process creation code
will be integrated. However, debuggability using CTRL-BRK is not the
main consideration. Instead, we will be designing our process invocation
architecture so as to make the best sense for the user. Besides, most
processes spawned by java will not be other java processes (no need).
xxxxx@xxxxx 2004-06-26
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |