the catalina.out log file for
the magic Tomcat Stopped message. Another option would be to actually
poll the port to see if it's available. They're both pretty ugly options.
- -chris
--
View this message in context:
http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12553588
Sent
asynchronous. Would get the job done though.
you
you could touch a file or something like that.
That would be a nice simple way of doing it. Will give that a shot on
Monday.
Cheers,
Derek
--
View this message in context:
http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12558158
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek,
Derek Alexander wrote:
Have been looking at the source, although not documented (for TC5.5), it
seems that it is possible to nest a Listener element
(org.apache.catalina.LifecycleListener) under the Server element as
that won't
return until the ports have been released at least?
Cheers,
Derek
--
View this message in context:
http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12525265
Sent from the Tomcat - User mailing list archive at Nabble.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek,
Derek Alexander wrote:
Using:
$CATALINA_HOME/bin/catalina.sh stop
$CATALINA_HOME/bin/catalina.sh start
in quick succession to restart Tomcat,
it is possible that the start operation will run before all ports have been
released by the
