Thanks for the suggestion, Dan. Sound like that option would be perfect, but I do not see it for Tomcat 5.5 (https://tomcat.apache.org/tomcat-5.5-doc/config/systemprops.html). Is there a work-around or alternative for users of older Tomcat versions?
Marc On Thu, Nov 10, 2011 at 11:43 AM, Daniel Mikusa <dmik...@vmware.com> wrote: > Marc, > > Take a look at "org.apache.catalina.startup.EXIT_ON_INIT_FAILURE". > > >From the docs... > > "If true, the server will exit if an exception happens during the server > initialization phase. If not specified, the default value of false will > be used." > > https://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html > > Dan > > > On Thu, 2011-11-10 at 08:32 -0800, Marc Limotte wrote: >> Hi. >> >> For reference, my set up is Tomcat 5.5.27, Java 1.6.0_22 , Ubuntu 10.04.3. >> >> Once in a while when starting Tomcat; ContextInitialization fails for >> my app (specifically, Spring DI fails), but the app still comes up in >> a broken state. Is there a way to make this a hard fail-- Ideally >> tomcat wouldn't start at all and would exit with a non-zero exit code? >> >> I'm separately investigating why Initialization fails, but at this >> time I'm looking for an easier way for our automated tools to know >> immediately that there is a problem (regardless of what the problem >> is). >> >> thanks, >> Marc >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
