Linux Red Hat Advanced Server and the Kill Command

rlangsto · 03-21-2005, 12:37 PM

Generally when attempting to create a stack trace on a java
process in unix. I can used the kill -3 (sigquit) command to create a thread dumps into a log file.
At times it is necessary to do this multiple times to view
the exact deadlock.
I have ran into an interesting issue where this command

> Kill -3 <pid>
is terminating the process. I have been looking for reasons
this may happen. I have tested it in various Redhat and Suse
configurations and cannot reproduce it.

Anyone have any thoughts ?

rlangsto · 03-24-2005, 12:47 PM

Update to this thread,
the resolution to this problem wasn't o/s , it was a communications issue between myself and the person to whom I gave instructions.
It turns out the user was killing the parent thread instead of the java process thread.
which point back to a real old axiom,
if it doesn't sound right,
and doesn't smell right,
it probably isn't right.