-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? - -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+VYfIACgkQ9CaO5/Lv0PAkGgCfYpk2VWmy2sYRmVQXSQu/pLZS SskAoJnS1aUGHBMZZk+mZY82Zie9aG2x =Czs4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
