Marc,
Yep, think you're right. My fault for not paying closer attention to
your version.
Other options that come to mind...
- fetch one of the URL's for your application, check for a 404 status
- connect via JMX, look at "Catalina:type=Deployer,host=localhost"
(substitute your host name for lo
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
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/s
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 woul
