-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
keeplearning,
On 9/2/2009 3:09 PM, keeplearning wrote:
Sorry. But I didn't understand how using 2 terminals would help me with the
questions I posted.
Then you need to do a 'man tee' and consider what Jim's trick is
actually doing.
- -chris
FWIW, I usually do a tail/tee on catalina.out in a term, then do the
kill -QUIT tomcat PID from another term, then kill the tail/tee
combo which leaves me with a reasonably clean thread dump.
For example:
Terminal A:
prompt$ tail -f /usr/local/tomcat/logs/catalina.out | tee
From: keeplearning [mailto:p_sodh...@yahoo.com]
Subject: thread dumps catalina.out
I have been told that if I do kill -3 process id, it will
send the thread dumps to catalina.out.
I prefer to use jstack, since I can control where the output goes for each dump.
- Chuck
THIS
Sorry. But I didn't understand how using 2 terminals would help me with the
questions I posted.
Jim Cox-2 wrote:
FWIW, I usually do a tail/tee on catalina.out in a term, then do the
kill -QUIT tomcat PID from another term, then kill the tail/tee
combo which leaves me with a reasonably
On 02.09.2009 21:05, Jim Cox wrote:
FWIW, I usually do a tail/tee on catalina.out in a term, then do the
kill -QUIT tomcat PID from another term, then kill the tail/tee
combo which leaves me with a reasonably clean thread dump.
For example:
Terminal A:
prompt$ tail -f
Nothing magical to the two terms, just makes it easier to have a
tail/tee combo running while issuing the kill -QUIT cmd (v. via job
control, e.g).
For example, in terminal A:
prompt#tail -f /usr/local/tomcat/logs/catalina.out | tee /tmp/tomcat.dump.A
Now in terminal B:
prompt#ps -aef | egrep
