Re: Tomcat 5.5.25 takes 5 minutes to shut down.
Hi Hermansen, Check the solution in the following link: http://www.ngasi.com/ngasihelp/ngasiuserguide/tomcat_fails_shutdown_complete.htm Hermansen, Erik wrote: Hello! I'm running Tomcat 5.5.25 on SLED 10. I performed the installation of Tomcat manually, using the apache-tomcat-5.5.25 archive from Apache's website. Tomcat will start fine and operate as expected, but shutting down is unreliable and often takes about 5 minutes to complete. If I run the $CATALINA_BASE/bin/shutdown.sh script, it will return immediately without errors, but checking for the process (ps aux | grep tomcat) shows it is still loaded for a long amount of time after the script is called. On a different server with identical hardware and very similar tomcat installation, the shutdown script will bring Tomcat down in about 3 seconds. Reading through catalina.out, I find this error which corresponds to calling the shutdown.sh script: SEVERE: Protocol handler pause failed java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.init(Socket.java:310) at java.net.Socket.init(Socket.java:154) at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:49 2) at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:289) at org.apache.jk.server.JkMain.pause(JkMain.java:681) at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:163) at org.apache.catalina.connector.Connector.pause(Connector.java:1032) at org.apache.catalina.core.StandardService.stop(StandardService.java:48 9) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734) at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) at org.apache.catalina.startup.Catalina.start(Catalina.java:577) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Sep 19, 2007 3:11:55 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Sep 19, 2007 3:11:56 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Sep 19, 2007 3:11:56 AM org.apache.catalina.core.AprLifecycleListener lifecycleE vent INFO: Failed shutdown of Apache Portable Runtime I've found a couple similar cases where people had this problem. They resolved it by doing something with their network configuration, but in both cases the description of their solution was very vague, so I'm not sure how I could proceed. -Erik -- Regards Gabe Wong Private JVM JAVA Hosting Automation http://www.ngasi.com - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5.25 takes 5 minutes to shut down.
Hello! I'm running Tomcat 5.5.25 on SLED 10. I performed the installation of Tomcat manually, using the apache-tomcat-5.5.25 archive from Apache's website. Tomcat will start fine and operate as expected, but shutting down is unreliable and often takes about 5 minutes to complete. If I run the $CATALINA_BASE/bin/shutdown.sh script, it will return immediately without errors, but checking for the process (ps aux | grep tomcat) shows it is still loaded for a long amount of time after the script is called. On a different server with identical hardware and very similar tomcat installation, the shutdown script will bring Tomcat down in about 3 seconds. Reading through catalina.out, I find this error which corresponds to calling the shutdown.sh script: SEVERE: Protocol handler pause failed java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.init(Socket.java:310) at java.net.Socket.init(Socket.java:154) at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:49 2) at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:289) at org.apache.jk.server.JkMain.pause(JkMain.java:681) at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:163) at org.apache.catalina.connector.Connector.pause(Connector.java:1032) at org.apache.catalina.core.StandardService.stop(StandardService.java:48 9) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734) at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) at org.apache.catalina.startup.Catalina.start(Catalina.java:577) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Sep 19, 2007 3:11:55 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Sep 19, 2007 3:11:56 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Sep 19, 2007 3:11:56 AM org.apache.catalina.core.AprLifecycleListener lifecycleE vent INFO: Failed shutdown of Apache Portable Runtime I've found a couple similar cases where people had this problem. They resolved it by doing something with their network configuration, but in both cases the description of their solution was very vague, so I'm not sure how I could proceed. -Erik
Re: Tomcat 5.5.25 takes 5 minutes to shut down.
Ive seen this too where the main process is stopped but the connections to the Listener stay alive for a while netstat -a | grep Port shows activity until all the connections are quiesced.. Ive see where commenting out the APR listener allows a quicker stop for tomcat e.g. !-- Listener className=org.apache.catalina.core.AprLifecycleListener/ -- M-- - Original Message - From: Gabe Wong [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Monday, September 24, 2007 3:53 PM Subject: Re: Tomcat 5.5.25 takes 5 minutes to shut down. Hi Hermansen, Check the solution in the following link: http://www.ngasi.com/ngasihelp/ngasiuserguide/tomcat_fails_shutdown_complete htm Hermansen, Erik wrote: Hello! I'm running Tomcat 5.5.25 on SLED 10. I performed the installation of Tomcat manually, using the apache-tomcat-5.5.25 archive from Apache's website. Tomcat will start fine and operate as expected, but shutting down is unreliable and often takes about 5 minutes to complete. If I run the $CATALINA_BASE/bin/shutdown.sh script, it will return immediately without errors, but checking for the process (ps aux | grep tomcat) shows it is still loaded for a long amount of time after the script is called. On a different server with identical hardware and very similar tomcat installation, the shutdown script will bring Tomcat down in about 3 seconds. Reading through catalina.out, I find this error which corresponds to calling the shutdown.sh script: SEVERE: Protocol handler pause failed java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.init(Socket.java:310) at java.net.Socket.init(Socket.java:154) at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:49 2) at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:289) at org.apache.jk.server.JkMain.pause(JkMain.java:681) at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:163) at org.apache.catalina.connector.Connector.pause(Connector.java:1032) at org.apache.catalina.core.StandardService.stop(StandardService.java:48 9) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734) at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) at org.apache.catalina.startup.Catalina.start(Catalina.java:577) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Sep 19, 2007 3:11:55 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Sep 19, 2007 3:11:56 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Sep 19, 2007 3:11:56 AM org.apache.catalina.core.AprLifecycleListener lifecycleE vent INFO: Failed shutdown of Apache Portable Runtime I've found a couple similar cases where people had this problem. They resolved it by doing something with their network configuration, but in both cases the description of their solution was very vague, so I'm not sure how I could proceed. -Erik -- Regards Gabe Wong Private JVM JAVA Hosting Automation http://www.ngasi.com - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.5.25 takes 5 minutes to shut down.
The solution Gabe pointed to fixed the problem. I found that my hostname was set to an old IP address no longer in use. When I added an entry to the hosts file, the shutdown script finished quickly as expected. Martin, I decided not to try commenting out the listener, since at that point, nothing was broke. Thanks for the quick replies, guys! -Erik -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Sunday, September 24, 2000 2:52 PM To: Tomcat Users List Subject: Re: Tomcat 5.5.25 takes 5 minutes to shut down. Ive seen this too where the main process is stopped but the connections to the Listener stay alive for a while netstat -a | grep Port shows activity until all the connections are quiesced.. Ive see where commenting out the APR listener allows a quicker stop for tomcat e.g. !-- Listener className=org.apache.catalina.core.AprLifecycleListener/ -- M-- - Original Message - From: Gabe Wong [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Monday, September 24, 2007 3:53 PM Subject: Re: Tomcat 5.5.25 takes 5 minutes to shut down. Hi Hermansen, Check the solution in the following link: http://www.ngasi.com/ngasihelp/ngasiuserguide/tomcat_fails_shutdown_complete htm Hermansen, Erik wrote: Hello! I'm running Tomcat 5.5.25 on SLED 10. I performed the installation of Tomcat manually, using the apache-tomcat-5.5.25 archive from Apache's website. Tomcat will start fine and operate as expected, but shutting down is unreliable and often takes about 5 minutes to complete. If I run the $CATALINA_BASE/bin/shutdown.sh script, it will return immediately without errors, but checking for the process (ps aux | grep tomcat) shows it is still loaded for a long amount of time after the script is called. On a different server with identical hardware and very similar tomcat installation, the shutdown script will bring Tomcat down in about 3 seconds. Reading through catalina.out, I find this error which corresponds to calling the shutdown.sh script: SEVERE: Protocol handler pause failed java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.init(Socket.java:310) at java.net.Socket.init(Socket.java:154) at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:49 2) at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:289) at org.apache.jk.server.JkMain.pause(JkMain.java:681) at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:163) at org.apache.catalina.connector.Connector.pause(Connector.java:1032) at org.apache.catalina.core.StandardService.stop(StandardService.java:48 9) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734) at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) at org.apache.catalina.startup.Catalina.start(Catalina.java:577) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Sep 19, 2007 3:11:55 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Sep 19, 2007 3:11:56 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Sep 19, 2007 3:11:56 AM org.apache.catalina.core.AprLifecycleListener lifecycleE vent INFO: Failed shutdown of Apache Portable Runtime I've found a couple similar cases where people had this problem. They resolved it by doing something with their network configuration, but in both cases the description of their solution was very vague, so I'm not sure how I could proceed. -Erik -- Regards Gabe Wong Private JVM JAVA Hosting Automation http://www.ngasi.com - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
RE: Tomcat 5.5.25 takes 5 minutes to shut down.
From: Hermansen, Erik [mailto:[EMAIL PROTECTED] Subject: RE: Tomcat 5.5.25 takes 5 minutes to shut down. I decided not to try commenting out the listener, since at that point, nothing was broke. You must not comment out the APR listenter if you're actually using APR. If you're not using APR, it won't matter what you do with the listener. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
