From: James Lampert [mailto:jam...@touchtonecorp.com]
Subject: Shutdown.sh doesn't. At least not reliably. (7.0.25)
Or where I should look for indications of what it could be?
Can you take a thread dump of the Tomcat process after shutdown.sh has been
used?
If you take a thread dump you'll be able to see the state of both Tomcat's
threads and your own application's threads to see where it's hanging.
-Original Message-
From: James Lampert [mailto:jam...@touchtonecorp.com]
Sent: Tuesday, November 27, 2012 9:10 AM
To: Tomcat Users List
2012/11/27 James Lampert jam...@touchtonecorp.com:
Running Tomcat on various AS/400s (V6R1 or later OS), we've found that
shutdown.sh doesn't reliably shut down the server, and we frequently have to
shut it down forcibly (i.e., finding CATALINA on a WRKACTJOB, and giving it
a 4 with
Konstantin Kolinko wrote:
2. Shutdown command is sent to port 8005. (8009 is a port used by AJP
protocol connector).
Thanks. That at least clears up a misconception on my part. Researching
it cleared up another misconception on my part: that the Catalina job
directly owns the ports.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 11/27/12 1:13 PM, James Lampert wrote:
Konstantin Kolinko wrote:
2. Shutdown command is sent to port 8005. (8009 is a port used by
AJP protocol connector).
Thanks. That at least clears up a misconception on my part.
Researching it
Christopher Schultz wrote:
Maybe use DMPJVM? Sorry for the through-Google link [PDF]:
THANKS! Never heard of such a thing until you brought it to my
attention, and it's enough of an eye-opener that I would have gladly
forgiven even a through-LMGTFY link.
DMPJVM looks like it may be just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 11/27/12 3:56 PM, James Lampert wrote:
Christopher Schultz wrote:
Maybe use DMPJVM? Sorry for the through-Google link [PDF]:
THANKS! Never heard of such a thing until you brought it to my
attention, and it's enough of an eye-opener
