Didn't work. -3 doesn't kill it. I tried for several minutes. Then I
tried -6. That killed it, but I didn't get the core. Where do you
think it put it? I did this: 'kill -6 2393 2> error' error was empty.
Thanks,
Rick
Peter Crowther wrote:
From: Rick Cockerham [mailto:[EMAIL PROTECTED]
When I do a 'top' and look at the java threads I
have a few threads a day that never stop and eat the system.
[...]
how can I see what's going on in that thread?
I do not have console access to the machine, so it has to be
done through ssh.
Kill -3 on the head Java process. This should generate a textual thread
dump to stderr, even on the IBM JVM. The dump includes a stack trace
for each thread. That should get you started as to what the busy
threads are doing.
You may have to redirect stderr somewhere useful before doing this,
depending on your current logging settings.
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Rick Cockerham
Pocket Knife Software, Inc.
http://www.pocketknifesoftware.com
512-249-0467
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
