Hi.
Use `kill 34933` - this will stop all Tomcat's treads correctly (exactly
- this will send `kill -TERM 34933 instead of `kill -KILL 34933` which
is `kill -9` and really kill process imediatelly).
Unfortunatelly I'm not Java coder so I can't give you advice - why
exactly Tomcat doesn't
btw - you can use `jstack 34933` after you run shutdown.sh to see which
classes (files) still hold in memory.
16.02.2014 9:51, Tim Leung пишет:
I am running Tomcat 7.0.50 btw.
On Sat, Feb 15, 2014 at 11:47 PM, Tim Leung timleung1...@gmail.com wrote:
I am unable to shutdown tomcat. When I
From: Tim Leung [mailto:timleung1...@gmail.com]
Subject: Unable to shutdown tomcat
I am unable to shutdown tomcat. When I do ./shutdown.sh, I don't see any
error, but the process still seems to be running.
Likely one of your webapps started a thread that is still running, preventing
the
I did a kill -3, and see these messages written to catalina.out. Something
definitely doesn't seem right -
Feb 15, 2014 11:24:23 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was
Can someone please help me?
On Sun, Feb 16, 2014 at 12:05 PM, Tim Leung timleung1...@gmail.com wrote:
I did a kill -3, and see these messages written to catalina.out. Something
definitely doesn't seem right -
Feb 15, 2014 11:24:23 PM org.apache.catalina.core.AprLifecycleListener init
INFO:
2014-02-17 2:16 GMT+04:00 Tim Leung timleung1...@gmail.com:
Can someone please help me?
On Sun, Feb 16, 2014 at 12:05 PM, Tim Leung timleung1...@gmail.com wrote:
main prio=5 tid=7fe82c001800 nid=0x10448e000 runnable [10448b000]
java.lang.Thread.State: RUNNABLE
at
