I'm no developer, but I think perhaps you want to take a look at a LifecycleListener. Something along the lines of "when this Context starts, check to see if Oracle is up. Block until it is, when it is, continue to application initialization."
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html John > -----Original Message----- > From: Daniel Haynes [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 21, 2003 10:50 AM > To: Tomcat User List (E-mail) > Subject: Re-post: Tomcat 4.1.18 as Win2k/XP Service > > > We have Tomcat and Oracle (both as services) running on a > single box. Our > application uses poolman and works fine when starting Tomcat > on a manual > basis, but on a re-boot Oracle is not ready by the time the > application > attempts to make its connections. The resulting error leaves > Tomcat/application in an unrecoverable state. > > What is the easiest way to delay the Tomcat startup (by say a > minute) on > re-boot. The Tomcat service uses 'tomcat.exe' which I think > is created on > the install. We thought of adding a hacked delay to > startup.bat but changing > the service to use startup.bat didn't seem to work at all. > (Win2k service > dependencies don't work in the sense that that the Tomcat service only > depends on the starting of the Oracle service, and does not wait until > Oracle is fully initialised) > > Any ideas ? > > > > Daniel Haynes > > > > Rule Financial > > 30 Cannon Street > > London EC4M 6YN > > > --------------------------------------------------------------------- > 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]
