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, 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]>
