The trace is probably in the catalina.out log file (at least that's
where it goes for us running tc5.0.30)

Peter wrote:
> hi all;
> I just found out that in linux
> under the /proc generate a fold 26337
> does it the place which the information stores?
> any idea?
> thanks
>
> On 6/13/07, Peter <[EMAIL PROTECTED]> 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
>>
>>
>>
>>
>>
>> On 6/12/07, Jon Wingfield <[EMAIL PROTECTED]> wrote:
>> >
>> > Good question. I don't know. The last time I used JBuilder was way
>> back
>> > in 2000.
>> > The Borland site suggests an OptimizeIt profiler is present in
>> JBuilder
>> > for the Developer and Enterprise editions:
>> > http://info.borland.com/techpubs/jbuilder/
>> >
>> > Jon
>> >
>> > Peter wrote:
>> > > thank you for ideas
>> > >
>> > > i current using JBuider2006, what profiler can used in JBuider2006?
>> > >
>> > > thanks
>> > > peter
>> > >
>> > > On 6/12/07, Jon Wingfield <[EMAIL PROTECTED]> wrote:
>> > >>
>> > >> Chuck answered a similar query recently:
>> > >> http://marc.info/?l=tomcat-user&m=118113828210257&w=2
>> > >>
>> > >> Your servlets are serving long-running requests (or are in infinite
>> > >> loops, dead-locked etc) when you are trying to shutdown tomcat.
>> > >> The first thing I'd do in this situation is SIGQUIT tomcat to get a
>> > >> stackdump of the running threads.
>> > >> With that you can usually determine the changes you need to do to
>> > your
>> > >> servlets, if required.
>> > >> If the stackdump isn't a help I'd attach a profiler to see where
>> your
>> > >> servlets are spending the time. I like the one bundled with
>> netbeans.
>> > >> I'm sure others on the list have their own favourites.
>> > >>
>> > >> Jon
>> > >>
>> > >> Peter wrote:
>> > >> > hi all;
>> > >> > when i shutdown tomcat, i found following message in the
>> > catalina.out;
>> > >> >
>> > >> >
>> > >> > 2007-6-12 18:18:44 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > * Waiting for 6 instance(s) to be deallocated*
>> > >> > 2007-6-12 18:18:45 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > *Waiting for 6 instance(s) to be deallocated
>> > >> > *2007-6-12 18:18:46 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > *Waiting for 6 instance(s) to be deallocated
>> > >> > *2007-6-12 18:18:46 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > *Waiting for 333 instance(s) to be deallocated*
>> > >> > 2007-6-12 18:18:47 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > *Waiting for 333 instance(s) to be deallocated*
>> > >> > 2007-6-12 18:18:48 org.apache.catalina.core.StandardWrapper
>> unload
>> > >> > * Waiting for 333 instance(s) to be deallocated*
>> > >> >
>> > >> > anyone has a idea about the about messages, does it means that
>> > there
>> > >> > is dead
>> > >> > lock in the program?
>> > >> > or some connection are not closed?
>> > >> >
>> > >> > thank you for ideas!
>> > >> > 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]
>> > >>
>> > >>
>> > >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To start a new topic, e-mail: users@tomcat.apache.org
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>



---------------------------------------------------------------------
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