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 wo
Am Donnerstag, den 12.04.2012, 14:02 +0100 schrieb ma...@apache.org:
> Christoph Maser wrote:
>
> >Do you see any chance a request for feature in that direction would be
> >accpeted?
>
> Right now, no. I don't see a requirement that isn't met by the existing
Am Donnerstag, den 12.04.2012, 14:29 -0400 schrieb Christopher Schultz:
> It's worth mentioning that requests bound to sessions that were
> associated with the "old" version will continue to be serviced by the
> old version of the webapp.
>
> You said "new requests" but "new sessions" is more accu
;
> Mark
>
> Christoph Maser wrote:
>
> >Hi
> >
> >is there a way to externally influence the switch between versions with
> >the new parallel deployment method. As I understand it tomcat
> >automatically switches to the new version for new requests as soo
Hi
is there a way to externally influence the switch between versions with
the new parallel deployment method. As I understand it tomcat
automatically switches to the new version for new requests as soon as
the context with the new version is started. Instead I would like to
manually control wich
