How to shutdown Tomcat gracefully when hung???
I have run into a problem where Tomcat is hanging inside ofg JNI code. This causes the allocated thread to stay allocated. When I go to shutdown Tomcat, it responds with 'Waiting for 1 instance(s) to be deallocated'. Is there a way to shutdown Tomcat gracefully under this condition so that the contextDestroyed listener responds and I can get debug info??? John McClain Senior Software Engineer TCS Healthcare [EMAIL PROTECTED] (530)886-1700x235 Before you criticize someone, walk a mile in their shoes. That way, you'll be a mile from them, and you'll have their shoes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to shutdown Tomcat gracefully when hung???
Hi, Please don't cross-post to tomcat-dev and tomcat-user at the same time. Gracefully, probably not. Kill it. Yoav Shapira http://www.yoavshapira.com -Original Message- From: John MccLain [mailto:[EMAIL PROTECTED] Sent: Monday, October 25, 2004 11:38 AM To: Tomcat Dev List; Tomcat user list Subject: How to shutdown Tomcat gracefully when hung??? I have run into a problem where Tomcat is hanging inside ofg JNI code. This causes the allocated thread to stay allocated. When I go to shutdown Tomcat, it responds with 'Waiting for 1 instance(s) to be deallocated'. Is there a way to shutdown Tomcat gracefully under this condition so that the contextDestroyed listener responds and I can get debug info??? John McClain Senior Software Engineer TCS Healthcare [EMAIL PROTECTED] (530)886-1700x235 Before you criticize someone, walk a mile in their shoes. That way, you'll be a mile from them, and you'll have their shoes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: shutdown tomcat in command line error
Hi, One idea: instead of copying all around, do a clean installation, try start and stop out of the box, make sure that works for you. After that, apply your configuration changes slowly (possibly one at a time) to see which one causes this error. Yoav Shapira Millennium Research Informatics -Original Message- From: Hongsong Zhou [mailto:[EMAIL PROTECTED] Sent: Thursday, September 09, 2004 5:29 PM To: [EMAIL PROTECTED] Subject: shutdown tomcat in command line error Tomcat 5.5.1 in windows 2003 server I copy tomcat/conf to another folder, modified server.xml, copy startup.bat and shutdown.bat from tomcat/bin, setup CATALINA_BASE in new startup.bat and shutdown.bat, startup.bat works fine, when I try to run shutdown.bat, I got an error: Sep 9, 2004 4:21:54 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8219 Sep 9, 2004 4:21:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409) Caused by: java.lang.NullPointerException at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:8 75) at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:111 7) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1089) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:3 12) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleS uppo rt.java:119) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1043) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1055) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:425) at org.apache.catalina.core.StandardService.stop(StandardService.java:512) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2001) at org.apache.catalina.startup.Catalina.stop(Catalina.java:590) at org.apache.catalina.startup.Catalina.start(Catalina.java:565) ... 6 more Any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
shutdown tomcat in command line error
Tomcat 5.5.1 in windows 2003 server I copy tomcat/conf to another folder, modified server.xml, copy startup.bat and shutdown.bat from tomcat/bin, setup CATALINA_BASE in new startup.bat and shutdown.bat, startup.bat works fine, when I try to run shutdown.bat, I got an error: Sep 9, 2004 4:21:54 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8219 Sep 9, 2004 4:21:55 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409) Caused by: java.lang.NullPointerException at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:875) at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1117) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1089) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1043) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1055) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:425) at org.apache.catalina.core.StandardService.stop(StandardService.java:512) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2001) at org.apache.catalina.startup.Catalina.stop(Catalina.java:590) at org.apache.catalina.startup.Catalina.start(Catalina.java:565) ... 6 more Any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
can not shutdown tomcat from shutdown.sh (V4.06)
Hi guys: I am using tomcat 4.06 /AIX, after added some servlet in the web.xml , I can not shutdown the tomcat by using shutdown.sh command. the process still runing in the Unix. and I have to use kill -9 to stop the tomcat process. the servlet I added is very simple , it initialize my jdbc connection pool and create some shared objects. Can any one give me some hints ? Thanks and regards. Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: can not shutdown tomcat from shutdown.sh (V4.06)
Hi, I am using tomcat 4.06 /AIX, after added some servlet in the web.xml , I can not shutdown the tomcat by using shutdown.sh command. the process still runing in the Unix. and I have to use kill -9 to stop the tomcat process. the servlet I added is very simple , it initialize my jdbc connection pool and create some shared objects. Can any one give me some hints ? The day people start searching the archives of this list before posting, I will be a happier man indeed. Your servlet or code it uses is spawning non-daemon threads. You are responsible for interrupting and terminating those threads, as tomcat and the JVM cannot do it for you. Alternatively, if it's your own, you mark the threads as daemons so that the JVM will automatically terminate them. If you're writing your own connection pool, my suggestion is don't bother, use an existing implementation like DBCP. You can send the JVM a SIGQUIT after running shutdown.sh while the JVM process is still active to see what threads are running and preventing the process from exiting properly. This has been discussed numerous times on this list, so you can search the archives for more information. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot shutdown Tomcat gracefully
Hello, I saw that bug in the bug database http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20663 I also receive this exception with Tomcat 4.1.27 and Solaris. I'm just wondering why this bug has the Severity Blocker. Can someone tell me about the consequences of this bug? Are there any severe consequences (I mean like the session will not be serialized) Thanks in advance Regards Karin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cannot shutdown Tomcat gracefully
Howdy, People assign priorities when they submit issues. People also tend to exaggerate the importance of their own bugs. You should consider it more on a personal level, i.e. is it a blocker to you? Likely not. And no, it does not affect session serialization. Yoav Shapira Millennium ChemInformatics -Original Message- From: Krause Karin [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 4:54 AM To: '[EMAIL PROTECTED]' Subject: Cannot shutdown Tomcat gracefully Hello, I saw that bug in the bug database http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20663 I also receive this exception with Tomcat 4.1.27 and Solaris. I'm just wondering why this bug has the Severity Blocker. Can someone tell me about the consequences of this bug? Are there any severe consequences (I mean like the session will not be serialized) Thanks in advance Regards Karin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 4.1.27: cannot shutdown tomcat !!
Buongiorno ;) That's not an exception we see very often. Your server.xml still has the default shutdown port (8005)? Can you telnet to localhost:8005 and issue SHUTDOWN? Do you have a strange networking setup on this machine? During shutdown, tomcat tries to connect to the server shutdown port and issue the simple string command, SHUTDOWN. For safety, tomcat will only accept connections from localhost on the shutdown port. Yoav Shapira Millennium ChemInformatics -Original Message- From: Fabio Bazzani [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 12:29 PM To: Tomcat Users List Subject: tomcat 4.1.27: cannot shutdown tomcat !! I'm working with JDK 1.4.0 and tomcat 4.1.27. I'm in advanced development and unexpectedly I cannot shutdown Tomcat. I spent all day to try undertand the why ? shell error message: Stopping service Tomcat-Standalone java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:159) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:146) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:384) at org.apache.jk.server.JkMain.stop(JkMain.java:311) at org.apache.jk.server.JkCoyoteHandler.destroy(JkCoyoteHandler.java:181) at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:120 5) at org.apache.catalina.core.StandardService.stop(StandardService.java:546) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2225) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Does anybody know what happened ? Thank you. Fabio This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat 4.1.27: cannot shutdown tomcat !!
- Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 3:01 PM Subject: RE: tomcat 4.1.27: cannot shutdown tomcat !! Buongiorno ;) That's not an exception we see very often. Your server.xml still has the default shutdown port (8005)? YES Can you telnet to localhost:8005 and issue SHUTDOWN? NO Do you have a strange networking setup on this machine? I'm not connected to any network !! During shutdown, tomcat tries to connect to the server shutdown port and issue the simple string command, SHUTDOWN. For safety, tomcat will only accept connections from localhost on the shutdown port. Yoav Shapira Millennium ChemInformatics -Original Message- From: Fabio Bazzani [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 12:29 PM To: Tomcat Users List Subject: tomcat 4.1.27: cannot shutdown tomcat !! I'm working with JDK 1.4.0 and tomcat 4.1.27. I'm in advanced development and unexpectedly I cannot shutdown Tomcat. I spent all day to try undertand the why ? shell error message: Stopping service Tomcat-Standalone java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:159) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:146) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:384) at org.apache.jk.server.JkMain.stop(JkMain.java:311) at org.apache.jk.server.JkCoyoteHandler.destroy(JkCoyoteHandler.java:181) at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:120 5) at org.apache.catalina.core.StandardService.stop(StandardService.java:546) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2225) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Does anybody know what happened ? Thank you. Fabio This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
(errata corrige) tomcat 4.1.27: cannot shutdown tomcat !!
I'm sorry for previous wrong message !! This is the correct one !! see details down. Fabio - Original Message - From: Fabio Bazzani [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 4:03 PM Subject: tomcat 4.1.27: cannot shutdown tomcat !! - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 3:01 PM Subject: RE: tomcat 4.1.27: cannot shutdown tomcat !! Buongiorno ;) That's not an exception we see very often. Your server.xml still has the default shutdown port (8005)? YES Can you telnet to localhost:8005 and issue SHUTDOWN? YES, but how to issue shutdown ? Do you have a strange networking setup on this machine? I'm not connected to any network !! During shutdown, tomcat tries to connect to the server shutdown port and issue the simple string command, SHUTDOWN. For safety, tomcat will only accept connections from localhost on the shutdown port. Yoav Shapira Millennium ChemInformatics -Original Message- From: Fabio Bazzani [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 12:29 PM To: Tomcat Users List Subject: tomcat 4.1.27: cannot shutdown tomcat !! I'm working with JDK 1.4.0 and tomcat 4.1.27. I'm in advanced development and unexpectedly I cannot shutdown Tomcat. I spent all day to try undertand the why ? shell error message: Stopping service Tomcat-Standalone java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:159) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:146) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:384) at org.apache.jk.server.JkMain.stop(JkMain.java:311) at org.apache.jk.server.JkCoyoteHandler.destroy(JkCoyoteHandler.java:181) at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:120 5) at org.apache.catalina.core.StandardService.stop(StandardService.java:546) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2225) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Does anybody know what happened ? Thank you. Fabio This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 4.1.27: cannot shutdown tomcat !!
Howdy, Can you telnet to localhost:8005 and issue SHUTDOWN? NO This is probably the cause for your error. You have to be able to telnet (or otherwise connect via http) localhost port 8005 and issue the SHUTDOWN command. If you can't do it manually, tomcat won't be able to do it either ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: (errata corrige) tomcat 4.1.27: cannot shutdown tomcat !!
Howdy, Can you telnet to localhost:8005 and issue SHUTDOWN? YES, but how to issue shutdown ? Ah, OK, this is better. Just type SHUTDOWN and press enter. Tomcat looks for any TCP/IP connection with sending that string. See the Server configuration reference: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/server.html See the await() function here for the source code: http://cvs.apache.org/viewcvs/jakarta-tomcat-catalina/catalina/src/share /org/apache/catalina/core/StandardServer.java?rev=1.22content-type=text /vnd.viewcvs-markup Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat 4.1.27: cannot shutdown tomcat !!
shutdown with telnet is ok. It appears the message Stopping service Tomcat-Standalone on the shell but the Window does not close. Should I recompile the entire catalina source code ? Thank you fabio - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 4:28 PM Subject: RE: (errata corrige) tomcat 4.1.27: cannot shutdown tomcat !! Howdy, Can you telnet to localhost:8005 and issue SHUTDOWN? YES, but how to issue shutdown ? Ah, OK, this is better. Just type SHUTDOWN and press enter. Tomcat looks for any TCP/IP connection with sending that string. See the Server configuration reference: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/server.html See the await() function here for the source code: http://cvs.apache.org/viewcvs/jakarta-tomcat-catalina/catalina/src/share /org/apache/catalina/core/StandardServer.java?rev=1.22content-type=text /vnd.viewcvs-markup Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 4.1.27: cannot shutdown tomcat !!
Howdy, No, you don't need to recompile. My guess is you have non-daemon threads your webapp has started, and that's why the JVM can't exit. This is not a rare problem. You need to make sure any threads you start are either daemons (so the JVM kills them automatically) or are properly interrupted and terminated when your app is shutting down. Yoav Shapira Millennium ChemInformatics -Original Message- From: Fabio Bazzani [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 11:42 AM To: Tomcat Users List Subject: tomcat 4.1.27: cannot shutdown tomcat !! shutdown with telnet is ok. It appears the message Stopping service Tomcat-Standalone on the shell but the Window does not close. Should I recompile the entire catalina source code ? Thank you fabio - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 4:28 PM Subject: RE: (errata corrige) tomcat 4.1.27: cannot shutdown tomcat !! Howdy, Can you telnet to localhost:8005 and issue SHUTDOWN? YES, but how to issue shutdown ? Ah, OK, this is better. Just type SHUTDOWN and press enter. Tomcat looks for any TCP/IP connection with sending that string. See the Server configuration reference: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/server.html See the await() function here for the source code: http://cvs.apache.org/viewcvs/jakarta-tomcat-catalina/catalina/src/shar e /org/apache/catalina/core/StandardServer.java?rev=1.22content-type=tex t /vnd.viewcvs-markup Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat 4.1.27: cannot shutdown tomcat !!
I'm working with JDK 1.4.0 and tomcat 4.1.27. I'm in advanced development and unexpectedly I cannot shutdown Tomcat. I spent all day to try undertand the why ? shell error message: Stopping service Tomcat-Standalone java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:159) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:146) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:384) at org.apache.jk.server.JkMain.stop(JkMain.java:311) at org.apache.jk.server.JkCoyoteHandler.destroy(JkCoyoteHandler.java:181) at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1205) at org.apache.catalina.core.StandardService.stop(StandardService.java:546) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2225) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Does anybody know what happened ? Thank you. Fabio
Re: tomcat 4.1.27: cannot shutdown tomcat !!
connect is not a hostname, looks like there is something wrong with your networking on that machine, not Tomcat Filip - Original Message - From: Fabio Bazzani [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 9:29 AM Subject: tomcat 4.1.27: cannot shutdown tomcat !! I'm working with JDK 1.4.0 and tomcat 4.1.27. I'm in advanced development and unexpectedly I cannot shutdown Tomcat. I spent all day to try undertand the why ? shell error message: Stopping service Tomcat-Standalone java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:159) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:146) at org.apache.jk.common.ChannelSocket.destroy(ChannelSocket.java:384) at org.apache.jk.server.JkMain.stop(JkMain.java:311) at org.apache.jk.server.JkCoyoteHandler.destroy(JkCoyoteHandler.java:181) at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1205) at org.apache.catalina.core.StandardService.stop(StandardService.java:546) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2225) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Does anybody know what happened ? Thank you. Fabio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: shutdown tomcat
I've added a listener instance and notifications start working!
Thank you for the answer!
- Original Message -
From: Jon Wingfield [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 7:31 PM
Subject: Re: shutdown tomcat
So you added an instance of TestTomcatNotifications to a session as an
attribute? That's the only way you'll get HttpSessionActivationListener
events.
You added a listener element to your web.xml registering
TestTomcatNotifications as a HttpSessionListener?
On shutdown sessionDestroyed(...) doesn't get called because the
StandardManager persists sessions and doesn't destroy them.
Let us know if you still don't get the sessionWillPassivate(...) event
coz that would worry me.
Jon
Maksimenko Alexander wrote:
Hi!
I created the following implementation of
HttpSessionListener,HttpSessionActivationListener.
public class TestTomcatNotifications implements HttpSessionListener,
HttpSessionActivationListener {
public void sessionCreated(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionCreated(se));
}
public void sessionDestroyed(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDestroyed(se));
}
public void sessionWillPassivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionWillPassivate(se));
}
public void sessionDidActivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDidActivate(se));
}
}
So this class logs that some method was invoked only. But when I am shut
down tomcat neither sessionWillPassivate nor sessionDestroyed are been
invoked. In API Doc we can read that:
A container that migrates session between VMs or persists sessions is
required to notify all attributes bound to sessions implementing
HttpSessionActivationListener.
What's wrong?
P.S. I use org.apache.catalina.session.StandardManager implementation.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
shutdown tomcat
Hi!
I created the following implementation of
HttpSessionListener,HttpSessionActivationListener.
public class TestTomcatNotifications implements HttpSessionListener,
HttpSessionActivationListener {
public void sessionCreated(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionCreated(se));
}
public void sessionDestroyed(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDestroyed(se));
}
public void sessionWillPassivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionWillPassivate(se));
}
public void sessionDidActivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDidActivate(se));
}
}
So this class logs that some method was invoked only. But when I am shut down tomcat
neither sessionWillPassivate nor sessionDestroyed are been invoked. In API Doc we can
read that:
A container that migrates session between VMs or persists sessions is required to
notify all attributes bound to sessions implementing HttpSessionActivationListener.
What's wrong?
P.S. I use org.apache.catalina.session.StandardManager implementation.
Re: shutdown tomcat
So you added an instance of TestTomcatNotifications to a session as an
attribute? That's the only way you'll get HttpSessionActivationListener
events.
You added a listener element to your web.xml registering
TestTomcatNotifications as a HttpSessionListener?
On shutdown sessionDestroyed(...) doesn't get called because the
StandardManager persists sessions and doesn't destroy them.
Let us know if you still don't get the sessionWillPassivate(...) event
coz that would worry me.
Jon
Maksimenko Alexander wrote:
Hi!
I created the following implementation of
HttpSessionListener,HttpSessionActivationListener.
public class TestTomcatNotifications implements HttpSessionListener,
HttpSessionActivationListener {
public void sessionCreated(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionCreated(se));
}
public void sessionDestroyed(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDestroyed(se));
}
public void sessionWillPassivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionWillPassivate(se));
}
public void sessionDidActivate(HttpSessionEvent se) {
System.out.println(TestTomcatNotifications.sessionDidActivate(se));
}
}
So this class logs that some method was invoked only. But when I am shut down tomcat
neither sessionWillPassivate nor sessionDestroyed are been invoked. In API Doc we can
read that:
A container that migrates session between VMs or persists sessions is required to notify
all attributes bound to sessions implementing HttpSessionActivationListener.
What's wrong?
P.S. I use org.apache.catalina.session.StandardManager implementation.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: shutdown tomcat
Howdy, public class TestTomcatNotifications implements HttpSessionListener, Something like SessionListener01/SessionListener02/SessionListener03 from http://cvs.apache.org/viewcvs/jakarta-tomcat-catalina/tester/src/tester/ org/apache/tester/ would have saved you time ;) down tomcat neither sessionWillPassivate nor sessionDestroyed are been invoked. In API Doc we can read that: A container that migrates session between VMs or persists sessions is required to notify all attributes bound to sessions implementing HttpSessionActivationListener. What's wrong? Any attributes bound will be notified in the Attribute listener, not the activation listener. You can test that it works ;) The session destroyed event isn't happening because tomcat is persisting, not destroying, your sessions, as they are valid (haven't timed out or been invalidated). Set session-timeout to 1 min in your test webapp's web.xml and observe what happens. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Again... cannot completely shutdown tomcat with embeded RMIRegistery
Hi, I have a shutdown pb with tomcat4.1.24rpm ( linux kernel 2.4.21 and j2se1.4.2 ) since I'm using rmiregistery... To force RmiRegistery to unload, I implement a loop to empty completely the registery by unbinding bound objects and I try to unexport all objects I can I read the content of the registery after that, and it's empty. I wait about 30 seconds and after half of tomcat processes dies, but not all of them and if I do a netstat -a, the rmiregitery is always listening on port 1099 Is somebody's got an idea ? Thanks a lot because I have no more idea to solve that issue Mourad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cannot shutdown Tomcat with GLIBC in unstable
* Charles Baker [EMAIL PROTECTED] [1202 15:02]: I just tried to shutdown Tomcat 4.1.12-2 using Sun JDK 1.3.1_03 on my box running unstable. I got the following undefined symbol message and Tomcat does not shutdown. Does anyone have a suggestion for what I should do other than kill the Tomcat pids? I wonder if I do that will Tomcat be able to restart? Upgrade your version of Java - it looks like your C library is out of step with your JVM (glibc is the Linux c library). What version of Linux are you using? usmghdebian:~# /usr/share/tomcat4/bin/shutdown.sh Using CATALINA_BASE: /usr/share/tomcat4 Using CATALINA_HOME: /usr/share/tomcat4 Using CATALINA_TMPDIR: /usr/share/tomcat4/temp Using JAVA_HOME: /usr/local/java1.3 Error occurred during initialization of VM Unable to load native library: /usr/local/stow/jdk1.3.1_03/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference -- Rasputin :: Jack of All Trades - Master of Nuns -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Cannot shutdown Tomcat with GLIBC in unstable
I just tried to shutdown Tomcat 4.1.12-2 using Sun JDK 1.3.1_03 on my box running unstable. I got the following undefined symbol message and Tomcat does not shutdown. Does anyone have a suggestion for what I should do other than kill the Tomcat pids? I wonder if I do that will Tomcat be able to restart? usmghdebian:~# /usr/share/tomcat4/bin/shutdown.sh Using CATALINA_BASE: /usr/share/tomcat4 Using CATALINA_HOME: /usr/share/tomcat4 Using CATALINA_TMPDIR: /usr/share/tomcat4/temp Using JAVA_HOME: /usr/local/java1.3 Error occurred during initialization of VM Unable to load native library: /usr/local/stow/jdk1.3.1_03/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference usmghdebian:~# = [EMAIL PROTECTED] http://www.charleshbaker.com/~chb/ Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Cannot shutdown tomcat
Hi! I'm using tomcat 4.1.10, on Linux Red Hat. I set the environment vars (JAVA_HOME and CATALINA_HOME), when I start tomcat (startup.sh), seems all run ok, but when I try to shutdown it, ... the shell does not respond: [tomcat@telemako bin]$ ./shutdown.sh Using CATALINA_BASE: /usr/local/jakarta-tomcat-4.1.10 Using CATALINA_HOME: /usr/local/jakarta-tomcat-4.1.10 Using CATALINA_TMPDIR: /usr/local/jakarta-tomcat-4.1.10/temp Using JAVA_HOME: /usr/local/j2sdk1.4.1/ I must do a Ctrl + c, and then kill the first tomcat process, then the other tomcat process die. I have been searchin in the mailing-list responses, but I cannot find a solution, any idea Thanx Marc -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: startup/shutdown Tomcat on Linux
Neal, Assuming you're running a bash-like (sh, bash, ksh) shell then you would execute the Linux analogs of shutdown.bat or startup.bat, which are named shutdown.sh and startup.sh respectively. So you would type the following from the console (no brackets in actual input): [cd $CATALINA_HOME /bin ] OR [cd $TOMCAT_HOME/bin] depending on your version of Tomcat and how the respective environment was setup [./shutdown.sh] and that's it Since you have restarted the server you will need to restart Tomcat by rnunning the following from the console: [cd $CATALINA_HOME /bin ] OR [cd $TOMCAT_HOME/bin] depending on your version of Tomcat and how the respective environment was setup [./startup.sh] and he should start --- To be sure, you could configure the system to be started after boot (similar to an NT/2K Service) and assign him to one or more run-levels. This is a little more complicated and I believe there are already some how-tos in the archives on this topic. HTH. Ciao. --- Yousef Shemisa | [EMAIL PROTECTED] 650.365.9704 x12 NetUnderdogs Dynamically-driven Flash, eCommerce, and portal solutions for business http://www.netunderdogs.com http://www.netunderdogs.com/ - Original Message - From: neal [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Sunday, August 25, 2002 10:04 PM Subject: startup/shutdown Tomcat on Linux How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: startup/shutdown Tomcat on Linux
or if it is an option you might want to install the 4.0.4 rpm, it seems to install the rc.d scripts for you automatically Just use the .sh counterparts to the .bat files you used on Windows. If you want Tomcat to start when the system comes up (or, to use some jargon, enters the proper run level) you should find someone at your site who's familiar with Linux configuration. This can be handled manually, by editing startup and shutdown files in /etc/rc.d or, on many modern Linux -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: startup/shutdown Tomcat on Linux
hi neal with tomcat4.0.4 there are no default webapps. (Prior to this there was a root context pre-configured) If you are getting a page that says 'There is no context available to process this request' or something, then it's running. If you are getting the standard 'The page cannot be displayed' (IE) then it's not. Which do you get. Also the first thing u should do is check the logs... try /usr/java/jakarta-tomcat4.0.4/catalina.out maybe your answer is there. or... try typing 'ps -aux' at the command line. If you see about 10-20 references to a process like /usr/java/j2sdk1.4.0/bin/java -classpath /usr/local/tomcat/bin/bootstrap.jar:/usr/java/j2sdk1.4.0/lib. etc then tomcat is running. -Original Message- From: neal [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 2:59 PM To: Tomcat Users List Subject: RE: startup/shutdown Tomcat on Linux Thanks for the info. I set my TOMCAT_HOME (/usr/java/jakarta-tomcat4.0.4) and JAVA_HOME (/usr/java/j2sdk1.4.0_01) env variables as needed to run these commands. The commands appear to now run fine (startup for instance will list 4 env variables it is apparently referenceing - CATALINA_BASE, CATALINA_HOME, CATALINA_TMPDIR, JAVA_HOME) and control is returned to the shell ... but Tomcat still isn't returning any pages to my browser. It was working fine before I restarted the server. :-\ Any thoughts? Thanks. Neal -Original Message- From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 25, 2002 10:21 PM To: [EMAIL PROTECTED] Subject: Re: startup/shutdown Tomcat on Linux Neal, Just use the .sh counterparts to the .bat files you used on Windows. If you want Tomcat to start when the system comes up (or, to use some jargon, enters the proper run level) you should find someone at your site who's familiar with Linux configuration. This can be handled manually, by editing startup and shutdown files in /etc/rc.d or, on many modern Linux systems, by using a GUI front-end to those configuration files. However, there are several variants on the underlying scheme and the tools that expose it, so it's not feasible to instruct you on the details from what you've told us (i.e., simply that you're using Linux). Good luck. Randall Schulz Mountain View, CA USA At 22:04 2002-08-25, neal wrote: How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: startup/shutdown Tomcat on Linux
sh startup.sh sh is the shell. At 10:04 PM 8/25/2002 -0700, you wrote: How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
startup/shutdown Tomcat on Linux
How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: startup/shutdown Tomcat on Linux
Neal, Just use the .sh counterparts to the .bat files you used on Windows. If you want Tomcat to start when the system comes up (or, to use some jargon, enters the proper run level) you should find someone at your site who's familiar with Linux configuration. This can be handled manually, by editing startup and shutdown files in /etc/rc.d or, on many modern Linux systems, by using a GUI front-end to those configuration files. However, there are several variants on the underlying scheme and the tools that expose it, so it's not feasible to instruct you on the details from what you've told us (i.e., simply that you're using Linux). Good luck. Randall Schulz Mountain View, CA USA At 22:04 2002-08-25, neal wrote: How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: startup/shutdown Tomcat on Linux
Thanks for the info. I set my TOMCAT_HOME (/usr/java/jakarta-tomcat4.0.4) and JAVA_HOME (/usr/java/j2sdk1.4.0_01) env variables as needed to run these commands. The commands appear to now run fine (startup for instance will list 4 env variables it is apparently referenceing - CATALINA_BASE, CATALINA_HOME, CATALINA_TMPDIR, JAVA_HOME) and control is returned to the shell ... but Tomcat still isn't returning any pages to my browser. It was working fine before I restarted the server. :-\ Any thoughts? Thanks. Neal -Original Message- From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 25, 2002 10:21 PM To: [EMAIL PROTECTED] Subject: Re: startup/shutdown Tomcat on Linux Neal, Just use the .sh counterparts to the .bat files you used on Windows. If you want Tomcat to start when the system comes up (or, to use some jargon, enters the proper run level) you should find someone at your site who's familiar with Linux configuration. This can be handled manually, by editing startup and shutdown files in /etc/rc.d or, on many modern Linux systems, by using a GUI front-end to those configuration files. However, there are several variants on the underlying scheme and the tools that expose it, so it's not feasible to instruct you on the details from what you've told us (i.e., simply that you're using Linux). Good luck. Randall Schulz Mountain View, CA USA At 22:04 2002-08-25, neal wrote: How do you start and shutdown Tomcat on Linux? I'm (obvioulsy) a windows person. I am attempting to get my app running on Linux. From the /bin directory I attempted to call shutdown.bat. This didn't work so I restarted the server (shutdown -r now). When the server came back, Tomcat was no longer responding. Attempting to call the URLs pointing to Tomcat, I now get either (a) a DNS error or (b) a hung request that never comes back. I guess my ideal would be that Tomcat would auto-start upon reboot of the server. Is this easy to setup? In the near-term though I just need to know how to start/restart/shutdown tomcat. Thanks in advance! Neal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Shutdown Tomcat
Howdy, My two cents... Solaris 2.6 on an Ultra 10, tomcat 4.0.1, takes about 20 seconds for complete startup, less than five seconds for complete shutdown (process gone and everything). My setup right now has 3 webapps, one of which spawns a couple of threads (but takes care to terminate them appropriately)... Yoav Steve Brunton wrote: Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. -- Steve Brunton [EMAIL PROTECTED] Phone: 404-827-2756 Chief Engineer Enterprise SystemsOne CNN Center, Atlanta GA CNN Internet Technologies ICBM: 84W 23' 45 33N 45' 29 * I used to have a handle on life, but it broke. * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Shutdown Tomcat
Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. -- Steve Brunton [EMAIL PROTECTED] Phone: 404-827-2756 Chief Engineer Enterprise SystemsOne CNN Center, Atlanta GA CNN Internet Technologies ICBM: 84W 23' 45 33N 45' 29 * I used to have a handle on life, but it broke. * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Shutdown Tomcat
If the standard shutdown approach does not work, that is a bug. Whether the bug is in your code or in Tomcat is the next thing to be determined. What is *supposed* to happen: - Tomcat calls the destroy() method of all your servlets - (Tomcat 4.0 only) Tomcat calls the contextDestroyed() method of all your context event listeners (this was added in Servlet 2.3) - Tomcat exits gracefuly - The operating system process goes away. If this is not happening for you, the most likely explanations are one of the following: - You have a servlet whose destroy() method never returns, or for some reason takes longer to process than you have waited - You have started some threads of your own, have not marked them as daemon threads, and have not cleaned them up in a destroy() method. - There is some bug in Tomcat's shutdown processing. The quickest way to figure out whether it's Tomcat or not is to create a clean installation of Tomcat (from the binary distribution) and start it up and shut it down. If this works for you, then the problem is most likely in your application. If this doesn't work, there's something else wierd going on that should be reported as a Tomcat bug to the bug tracking system at: http://nagoya.apache.org/bugzilla/ Craig McClanahan On Wed, 31 Oct 2001, Evan Swanson wrote: Date: Wed, 31 Oct 2001 10:21:42 -0800 From: Evan Swanson [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE: Shutdown Tomcat Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? -Original Message- From: Bruno Crapart [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 8:35 AM To: Tomcat Users List Subject: RE: Shutdown Tomcat Ctrl + C. :) -Message d'origine- De : Fiona [mailto:[EMAIL PROTECTED]] Envoyé : mardi 30 octobre 2001 17:04 À : [EMAIL PROTECTED] Objet : Shutdown Tomcat Hi, I don't know how to shutdown Tomcat. I have tried to use the shutdown.bat but it doesn't seem to work. Do I have to edit it or give it any parameters? Regards Fiona. ___ Fiona McEvoy, PROSE, 20 Grantham Street, Dublin 8, Ireland. Email: [EMAIL PROTECTED] Tel. (+353 1) 4783511, Fax. (+353 1) 4783937. ___ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Shutdown Tomcat
I see the same problems that Evan mentions (solaris). It takes about 30-45 seconds to shutdown on a devel server with no users and only 1 (albeit large) servlet and a few dozen JSPs. Don't have any JDBC connections or anything else like that. Similarly, startup takes about 15-20 seconds. On windows it takes about 5 seconds. -Original Message- From: Steve Brunton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:29 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing, copying, forwarding or saving them and notify the sender immediately by reply e-mail. Zurich Capital Markets and its affiliates reserve the right to monitor all e-mail communications through its networks. Unless otherwise stated, any pricing information in this e-mail is indicative only, is subject to change and does not constitute an offer to enter into any transaction at such price and any terms in relation to any proposed transaction are indicative only and subject to express final confirmation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Shutdown Tomcat
Hi, I'm facing the same problem with Tomcat 3.2.1 When I call tomcat.sh stop it shows the PATH used for the classes and then it says Stop Tomcat. But when I try to restart it typing tomcat.sh start, it gives the following error: FATAL:java.net.BindException: Address already in use java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:408) at java.net.ServerSocket.init(ServerSocket.java:170) at java.net.ServerSocket.init(ServerSocket.java:121) at org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(DefaultServerS ocketFactory.java:97) at org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java :239) at org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnector.java:188) at org.apache.tomcat.core.ContextManager.start(ContextManager.java:527) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:202) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) Of course, it's a socket error meaning that it wasn't actually stopped... Ok, I can't figure out why... I see the same problems that Evan mentions (solaris). It takes about 30-45 seconds to shutdown on a devel server with no users and only 1 (albeit large) servlet and a few dozen JSPs. Don't have any JDBC connections or anything else like that. Similarly, startup takes about 15-20 seconds. On windows it takes about 5 seconds. -Original Message- From: Steve Brunton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:29 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing, copying, forwarding or saving them and notify the sender immediately by reply e-mail. Zurich Capital Markets and its affiliates reserve the right to monitor all e-mail communications through its networks. Unless otherwise stated, any pricing information in this e-mail is indicative only, is subject to change and does not constitute an offer to enter into any transaction at such price and any terms in relation to any proposed transaction are indicative only and subject to express final confirmation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Shutdown Tomcat
If you call shutdown.sh (or tomcat.sh stop) and then do ps -eaf |grep java you will most likely see the process still running for a while. Once it goes away you can restart. It won't restart 'cuz it hasn't shut down yet... hence, the port is still bound. -Original Message- From: Martin Mauri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:47 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Hi, I'm facing the same problem with Tomcat 3.2.1 When I call tomcat.sh stop it shows the PATH used for the classes and then it says Stop Tomcat. But when I try to restart it typing tomcat.sh start, it gives the following error: FATAL:java.net.BindException: Address already in use java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:408) at java.net.ServerSocket.init(ServerSocket.java:170) at java.net.ServerSocket.init(ServerSocket.java:121) at org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(DefaultServerS ocketFactory.java:97) at org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java :239) at org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnector.java:188) at org.apache.tomcat.core.ContextManager.start(ContextManager.java:527) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:202) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) Of course, it's a socket error meaning that it wasn't actually stopped... Ok, I can't figure out why... I see the same problems that Evan mentions (solaris). It takes about 30-45 seconds to shutdown on a devel server with no users and only 1 (albeit large) servlet and a few dozen JSPs. Don't have any JDBC connections or anything else like that. Similarly, startup takes about 15-20 seconds. On windows it takes about 5 seconds. -Original Message- From: Steve Brunton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:29 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing, copying, forwarding or saving them and notify the sender immediately by reply e-mail. Zurich Capital Markets and its affiliates reserve the right to monitor all e-mail communications through its networks. Unless otherwise stated, any pricing information in this e-mail is indicative only, is subject to change and does not constitute an offer to enter into any transaction at such price and any terms in relation to any proposed transaction are indicative only and subject to express final confirmation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing, copying, forwarding or saving them and notify the sender immediately by reply e-mail. Zurich Capital Markets and its affiliates reserve the right to monitor all e-mail communications through its networks. Unless otherwise stated, any
Re: Shutdown Tomcat
Rick, The last time I did the process below, I waited up to 30 minutes and nothing happened, how much am I supposed to wait then?? If you call shutdown.sh (or tomcat.sh stop) and then do ps -eaf |grep java you will most likely see the process still running for a while. Once it goes away you can restart. It won't restart 'cuz it hasn't shut down yet... hence, the port is still bound. -Original Message- From: Martin Mauri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:47 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Hi, I'm facing the same problem with Tomcat 3.2.1 When I call tomcat.sh stop it shows the PATH used for the classes and then it says Stop Tomcat. But when I try to restart it typing tomcat.sh start, it gives the following error: FATAL:java.net.BindException: Address already in use java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:408) at java.net.ServerSocket.init(ServerSocket.java:170) at java.net.ServerSocket.init(ServerSocket.java:121) at org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(DefaultServerS ocketFactory.java:97) at org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java :239) at org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnector.java:188) at org.apache.tomcat.core.ContextManager.start(ContextManager.java:527) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:202) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) Of course, it's a socket error meaning that it wasn't actually stopped... Ok, I can't figure out why... I see the same problems that Evan mentions (solaris). It takes about 30-45 seconds to shutdown on a devel server with no users and only 1 (albeit large) servlet and a few dozen JSPs. Don't have any JDBC connections or anything else like that. Similarly, startup takes about 15-20 seconds. On windows it takes about 5 seconds. -Original Message- From: Steve Brunton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 1:29 PM To: Tomcat Users List Subject: Re: Shutdown Tomcat Evan Swanson wrote: Yeah, I have been wondering the same thing. On unix is seems that you have to kill the process. Shutdown.bat and shutdown.sh do not seem to stop the Tomcat process. I am guessing they just log off all of the sessions 'gracefully' You then have to manually kill the process? I am not sure if this is a problem with tomcat or it is supposed to be that way. It seems to be the same effect when you use the manager application to shutdown tomcat so I am guessing that it was designed to work that way. I have been unable to find any doco on the subject. Does anybody know a better way of shutting down the server than killing the process? I've got Tomcat 4.0.1/JDK1.3.1_01 shutting down happily on Solaris x86 just spiffy like. It does seem to take it a while to spool everything down. Currently it's only loading about 10 servlets and if I tail the output log as the thing is shutting down I can see it hitting all the destroy() methods and shutting down JNDI, JDBC and LDAP connections. Make sure that all your servlets clean up after themselves and it should shutdown fine. This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing, copying, forwarding or saving them and notify the sender immediately by reply e-mail. Zurich Capital Markets and its affiliates reserve the right to monitor all e-mail communications through its networks. Unless otherwise stated, any pricing information in this e-mail is indicative only, is subject to change and does not constitute an offer to enter into any transaction at such price and any terms in relation to any proposed transaction are indicative only and subject to express final confirmation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] This email and any attachments are confidential and may be legally privileged. No confidentiality or privilege is waived or lost by any transmission in error. If you are not the intended recipient you are hereby notified that any use, printing, copying or disclosure is strictly prohibited. Please delete this email and any attachments, without printing
Re: Re[2]: IP binding for server shutdown (tomcat 4)
Jochen Schwoerer [EMAIL PROTECTED] wrote: It currently is hard coded to bind to 127.0.0.1, so it would take a code change to make this possible. will it be possible to configure it via server.xml in the final version? I believe it would be a security risk, people can DOS you on that port, and if you're not careful enough, shut down your Tomcat environment. (Be careful enough is choosing somehow a random pattern of more than 128bytes IMO). I would be strongly against from changing that code before (or after) the release. Pier
Re: Re[2]: IP binding for server shutdown (tomcat 4)
Jochen Schwoerer [EMAIL PROTECTED] wrote: Hello Pier, Saturday, September 08, 2001, 8:20:30 PM, you wrote: PF Jochen Schwoerer [EMAIL PROTECTED] wrote: hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? PF I believe that for security reasons, in the upcoming version, the binding PF will be allowed and done only to localhost (127.0.0.1) in our case we have a machine with multiple ip addresses and want to run several instances on different ips but with the same control ports. I don't see a valid reason on why this should be done, while I see a potential security hazard in binding on IPs != localhost. it would be good to have the possibilty to configure the binding ip like in the connector directive. Nope, it would not be... Because then people would play around with it, and security is compromised... One day we'll remove that shutdown mechanism all together Pier BTW, If you respond to one of my mailing list emails NOT to the mailing list, but CCing me, that message will not reach the right place, meaning that it will considered as SPAM, and go down the drain... Don't send me mail as CC or TO if on the CC or TO there's also a mailing list.
IP binding for server shutdown (tomcat 4)
hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? thanks in advance jochen schwoerer [EMAIL PROTECTED]
Re: IP binding for server shutdown (tomcat 4)
Jochen Schwoerer [EMAIL PROTECTED] wrote: hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? I believe that for security reasons, in the upcoming version, the binding will be allowed and done only to localhost (127.0.0.1) Pier
Re[2]: IP binding for server shutdown (tomcat 4)
Hello Craig, Saturday, September 08, 2001, 9:04:15 PM, you wrote: CRM On Sat, 8 Sep 2001, Jochen Schwoerer wrote: Date: Sat, 8 Sep 2001 20:14:01 +0200 From: Jochen Schwoerer [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], Jochen Schwoerer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: IP binding for server shutdown (tomcat 4) hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? CRM It currently is hard coded to bind to 127.0.0.1, so it would take a code CRM change to make this possible. will it be possible to configure it via server.xml in the final version? thanks in advance jochen schwoerer [EMAIL PROTECTED] CRM Craig McClanahan jochen schwoerer
Re: Re[2]: IP binding for server shutdown (tomcat 4)
Although, you can't control what IP address it binds to, you can control what port it listens on. I'm guessing the easiest solution to your problem would be to just set each of the different Tomcat installations up to use a different port? I think you basically, just need to change the following line in server.xml. Server port=8005 shutdown=SHUTDOWN debug=0 Jon - Original Message - From: Jochen Schwoerer [EMAIL PROTECTED] To: Pier Fumagalli [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, September 08, 2001 1:27 PM Subject: Re[2]: IP binding for server shutdown (tomcat 4) Hello Pier, Saturday, September 08, 2001, 8:20:30 PM, you wrote: PF Jochen Schwoerer [EMAIL PROTECTED] wrote: hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? PF I believe that for security reasons, in the upcoming version, the binding PF will be allowed and done only to localhost (127.0.0.1) in our case we have a machine with multiple ip addresses and want to run several instances on different ips but with the same control ports. it would be good to have the possibilty to configure the binding ip like in the connector directive. PF Pier jochen schwoerer [EMAIL PROTECTED]
Re[4]: IP binding for server shutdown (tomcat 4)
Hello Jonathan, Sunday, September 09, 2001, 12:06:33 AM, you wrote: JEM Although, you can't control what IP address it binds to, you can control JEM what port it listens on. I'm guessing the easiest solution to your problem JEM would be to just set each of the different Tomcat installations up to use a JEM different port? I think you basically, just need to change the following JEM line in server.xml. JEM Server port=8005 shutdown=SHUTDOWN debug=0 i know this solution but i think this one is not clean. we want to keep the different instances completely independant from each other. i have looked around a bit in the source code: i think there must be changes in Server.java and StandardServer.java. maybe this can be done until the final version will be released. jochen schwoerer [EMAIL PROTECTED] JEM Jon JEM - Original Message - JEM From: Jochen Schwoerer [EMAIL PROTECTED] JEM To: Pier Fumagalli [EMAIL PROTECTED] JEM Cc: [EMAIL PROTECTED] JEM Sent: Saturday, September 08, 2001 1:27 PM JEM Subject: Re[2]: IP binding for server shutdown (tomcat 4) Hello Pier, Saturday, September 08, 2001, 8:20:30 PM, you wrote: PF Jochen Schwoerer [EMAIL PROTECTED] wrote: hello all, does somebody know if it is possible to bind the shutdown listener of tomcat 4 on a specific ip address like it is possible for connectors? PF I believe that for security reasons, in the upcoming version, the JEM binding PF will be allowed and done only to localhost (127.0.0.1) in our case we have a machine with multiple ip addresses and want to run several instances on different ips but with the same control ports. it would be good to have the possibilty to configure the binding ip like in the connector directive. PF Pier jochen schwoerer [EMAIL PROTECTED]
Error when shutdown tomcat
Hi, When I run the shutdown.bat I got the following errors: ... Is the error comes from the configuration or a bug in the tomcat? Thanks. J. Tang
Re: I can shutdown Tomcat
Mauricio, If you are running Unix you can do it the dirty way by killing the process. I have found that Tomcat has some problems shutting down if the AJp connector is not enabled. Duane On Tue, 7 Nov 2000, [iso-8859-1] Mauricio Nuñez wrote: Thanks for your attention: I can't shutdown one of my sites, running Tomcat. I can shutdown others 3 sites, but this not. What alternative i have? Any comment,tip, tool is wellcome. thanks in advance Mauricio Nuñez
Re: I can shutdown Tomcat
Mauricio Nuñez wrote: Thanks for your attention: I can't shutdown one of my sites, running Tomcat. I can shutdown others 3 sites, but this not. What alternative i have? Any comment,tip, tool is wellcome. thanks in advance Mauricio Nuñez the shutdown uses the port indicated in the server.xml file to communicate with the servlet runner, if you have changed the port since you started tomcat it will not be able to shutdown? If this isn't your problem mayb eyou should be more specific, what error is being reported, how are you starting it?
