-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pid,
On 4/23/12 9:50 PM, Pid wrote: > On 23/04/2012 15:06, Christopher Schultz wrote: >> Christoph, >> >> On 4/22/12 11:55 AM, Christoph Maser wrote: >>> Chris, >> >>> Am Donnerstag, den 19.04.2012, 18:21 +0200 schrieb Christopher >>> Schultz: >>>> Christoph, >>>> >>>> What about the webapp itself performing its own health-check >>>> as a last step of deployment, and throwing an exception >>>> (thereby preventing Tomcat from bringing it into service) if >>>> things aren't in working order? >> >>> this is the obvious way to do it as it is now. As I said >>> before that way one looses the access to the wapps status >>> pages. >> >> So you want the webapp both up (for status) and down (for >> traffic) at the same time? Tomcat certainly can't manage that for >> you. >> >> If you need "status" on a failed-deployment, why not dump it to a >> file or something like that? > > Or use JMX rather than HTTP to acquire status information. In theory that sounds good, but the webapp needs to be deployed in order to interrogate it via JMX. Once it's deployed, it's in service (even if it's broken) and the system falls apart. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+YEPUACgkQ9CaO5/Lv0PB+PQCcChgwpeR0ODTcnn8+RiOHFdaR mOwAoJcHd4fb6hTUf+Zy3OkpgfV2G97o =o1DV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
