Nikolaos I also have this problem. In my case, apache must only start if the conf/auto/modjk.conf has been written. From the time that startup.sh finishes to when it's safe to start apache is 30 or so seconds. The wait time is variable, so a 30 second sleep in my /etc/init.d reboot script might work today but fail in the future.
My vote would be to have startup.sh exit when tomcat processed all the code it needs. If you come up with a solution, please let me know. David > -----Original Message----- > From: Nikolaos Giannopoulos [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 29, 2003 10:01 AM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1.12/18 Startup Delay > > > Hi, > > Is there any reason why Tomcat 4.1.12 and 4.1.18 (on Solaris > 8, Sun E450 > Dual 400MHz 1GB RAM) requires about 10-15 second delay after > the startup.sh > script is executed before it can process requests. We have > observed the > same situation on other boxes. > > Essentially startup.sh returns quite quickly after the script > is executed > but if you attempt to invoke servlets on it they fail (until 10 or so > seconds after the script returns). > > We noticed this with our RC (server reboot) script and had to > manually enter > a "sleep 15" between Tomcat startup and our apps startup > OTHERWISE our app > would not startup properly as it immediately tries to > initialize servlets > and fails. > > Shouldn't startup.sh return *only* when Tomcat is able to > service requests? > > --Nikolaos > > > > > > --------------------------------------------------------------------- > 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]
