Shutdown command does not terminate tomcat process

2010-05-29 Thread /U 

I use tomcat6 on Linux. I run tomcat with shutdown port
configured as follows:
  Server port=8005 shutdown=SHUTDOWN
//...

After I start tomcat, I find that:

# jps -l
24819 org.apache.catalina.startup.Bootstrap
25103 sun.tools.jps.Jps
# 

Now when I issue SHUTDOWN command to tcp/8005, logs show that the
connectors are being shutdown:

   May 29, 2010 3:11:55 PM org.apache.coyote.http11.Http11Protocol pause
   INFO: Pausing Coyote HTTP/1.1 on http-8080
   May 29, 2010 3:11:55 PM org.apache.coyote.http11.Http11Protocol pause
   INFO: Pausing Coyote HTTP/1.1 on http-8443
   May 29, 2010 3:11:56 PM org.apache.catalina.core.StandardService stop
   INFO: Stopping service Catalina
   May 29, 2010 3:11:57 PM org.apache.coyote.http11.Http11Protocol destroy
   INFO: Stopping Coyote HTTP/1.1 on http-8080
   May 29, 2010 3:11:57 PM org.apache.coyote.http11.Http11Protocol destroy
   INFO: Stopping Coyote HTTP/1.1 on http-8443

But I find that the process is till running:

# jps -l
24819 org.apache.catalina.startup.Bootstrap
25103 sun.tools.jps.Jps
# 

why does this happen? Does not shutdown command to shutdown port
kill tomcat?

pl help,

/U


-- 
View this message in context: 
http://old.nabble.com/Shutdown-command-does-not-terminate-tomcat-process-tp28719038p28719038.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Shutdown command does not terminate tomcat process

2010-05-29 Thread Caldarale, Charles R 
 From: /U [mailto:uma...@comcast.net]
 Subject: Shutdown command does not terminate tomcat process
 
 But I find that the process is till running:
 
 # jps -l
 24819 org.apache.catalina.startup.Bootstrap
 25103 sun.tools.jps.Jps
 #
 
 why does this happen? Does not shutdown command to shutdown port
 kill tomcat?

You most likely have a webapp that has started a thread on its own, and has 
failed to clean up properly when the webapp is stopped.  If you take a thread 
dump, you should be able to see the rogue thread.  Normally, one uses a 
ServletContextListener to stop your asynchronous threads during webapp or 
container termination.

Note that there's a FAQ entry for this situation:
http://wiki.apache.org/tomcat/FAQ/Miscellaneous#Q25

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org