mdxyz - thanks for the test.war - helped alot with confirming this issue.
I was able to confirm this problem using the init script.
There are two ways of shutting down a running tomcat6 instance:
1) Send it the TERM signal - this is what the init script does through start-stop-daemon; when tomcat is shutdown this way I see no logging of any description.
2) Use the /usr/share/tomcat6/bin/shutdown.sh script to connect to the shutdown port (normally 8005) and initiate the shutdown that way: shutting down the tomcat6 instance this way results in correct shutdown logging to /var/log/tomcat6:
mdxyz - thanks for the test.war - helped alot with confirming this issue.
I was able to confirm this problem using the init script.
There are two ways of shutting down a running tomcat6 instance:
1) Send it the TERM signal - this is what the init script does through start-stop-daemon; when tomcat is shutdown this way I see no logging of any description.
2) Use the /usr/share/ tomcat6/ bin/shutdown. sh script to connect to the shutdown port (normally 8005) and initiate the shutdown that way: shutting down the tomcat6 instance this way results in correct shutdown logging to /var/log/tomcat6:
19-Aug-2011 14:32:49 org.apache. coyote. http11. Http11Protocol pause catalina. core.StandardSe rvice stop test.TestDestro y destroy coyote. http11. Http11Protocol destroy
INFO: Pausing Coyote HTTP/1.1 on http-8080
19-Aug-2011 14:32:50 org.apache.
INFO: Stopping service Catalina
19-Aug-2011 14:32:50 de.mdiener.
WARNING: destroy
19-Aug-2011 14:32:50 org.apache.
INFO: Stopping Coyote HTTP/1.1 on http-8080
I would suspect that sending the process the TERM signal differs from initiating a tomcat controlled shutdown; I'll take a look at the source and see.