its an asynchronous call, all shutdown.sh does, is connect to the
shutdown port and issue the shutdown command,
when shutdown.sh returns, there is no guarantee that the java process
has been shutdown, that depends on the webapplications installed
Filip
brycenesbitt wrote:
Odd. I call
-restarting-tomcat-without-risk-of-java.net.BindException-tf2649674.html#a9762592
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail
the problem you are having is because you didn't shutdown the java process.
invoking shutdown.sh when your tomcat instance has suffered a memoryleak
doesn't guarantee that it will stop, or how long it takes to stop it.
you must ensure the process is killed properly
Filip
Bryce Nesbitt wrote:
Bryce Nesbitt wrote:
Do we have to wait at least 20 seconds to be sure the port is clear?
The easiest thing is to do 'killall -9 java' ;-)
I run Tomcat under its own account. And restart script looks like this:
#!/bin/sh
~/bin/shutdown.sh
sleep 10
killall -9 java
~/bin/startup.sh
There's
We have a Tomcat application, which binds to port 8080 and AJP 6135. At
3 am we restart this application (because of a memory leak). But
sometimes it is unable to bind to it's own port, and it just dies and
never starts. Naturally this causes unhappiness. The server.xml is:
Connector
