thank you i got that

On 6/16/07, Rainer Jung <[EMAIL PROTECTED]> wrote:

Are you actually using -Xrs? At least it's not contained in the part of
the commandline you posted, which is unfortunately truncated.

The result of kill -QUIT goes to STDOUT of the jvm. So you need to find
out, where your STDOUT goes to. The standard tomcat start scripts
(startup.sh or catalina.sh called with the argument start) redirect
STDOUT to logs/catalina.out.

Regards,

Rainer

Peter wrote:
> hi all;
> i try to use SIGQUIT but can not see the stack trace.
>
> [EMAIL PROTECTED] root]# ps -ef|grep tomcat
> root     26337     1  5 09:45 pts/0    00:00:11
> /usr/java/jre1.5.0_08/bin/java -Xms256m -Xmx512m -
> Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -
> Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties -
> Djava.endorsed.dirs=/opt/tomcat/common/endorsed -classpath
> :/opt/tomcat/bin/bootstrap.ja
> root     26427 26172  0 09:49 pts/0    00:00:00 grep tomcat
>
> [EMAIL PROTECTED] root]# kill -SIGQUIT 26337
> [EMAIL PROTECTED] root]# kill -3 26337
> [EMAIL PROTECTED] root]#
>
> does anyone has idea why?
> some artical said that if JVM set -Xrs,it will ignore the OS signal like
> SIGQUIT
> Does anyone know how can i see the stack trace in this situation?
> i use Tomcat 5.5.20 in  linux , java, 1.5.0_10
>
> thanks


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to