Peter and all,
Earlier was from my MAC. This thread dump is from RedHat (production
server).
Your help is much appreciated.
Attaching to process ID 12649, please wait...
Debugger attached successfully.
Client compiler detected.
JVM version is 1.5.0_09-b01
Thread 12649: (state = BLOCKED)
From: Maduranga Kannangara [mailto:[EMAIL PROTECTED]
Below is my dump and thanks a lot for your time.
[...]
Thread [EMAIL PROTECTED]: (state = BLOCKED)
- java.lang.Thread.sleep(long) @bci=0 (Interpreted frame)
- org.quartz.core.QuartzSchedulerThread.run() @bci=870, line=420
(Interpreted
Hi,
A friend of mine said it was not due to ActiveMQ that Tomcat does not
shutdown properly, however I added a kill command to shutdown.sh script
which is NOT good at all, I understand.
In MAC (10.5) kill -3 seems working, but its a blind path which gets me
nowhere. I do not get a trace of the
From: Maduranga Kannangara [mailto:[EMAIL PROTECTED]
What I need simply is a clean shutdown on Tomcat :-)
Yes. In order to *get* that clean shutdown, you need to find out what's
preventing it :-).
One common problem is that something in your webapp has created a thread and
not marked it as
Thanks a lot Peter! I got a thread dump using jstack 704 (PID was 704)
I think I need a little more of your help to find out where exactly going
wrong. Below is my dump and thanks a lot for your time.
MadurangaMAC:bin Maduranga$ jstack 704
Attaching to process ID 704, please wait...
Debugger
From: Maduranga Kannangara [mailto:[EMAIL PROTECTED]
There is an issue with my Tomcat instance where I have to
kill it using 9 all the time.
This is my application environment:
An active-mq queue is used inside my application war.
Tomcat version: 5.x
OS: Redhat Linux
It would help if you
Tomcat: 5.5.20
JVM: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
However, this also same behavior on OSX 10.5 as well.
With JVM: Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_13-b05-237)
I need