-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 4/25/12 4:21 PM, Pid wrote:
> On 25/04/2012 15:57, Christopher Schultz wrote:
>> 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 wro
On 25/04/2012 15:57, Christopher Schultz wrote:
> 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
-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:
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
-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 deplo
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph,
On 4/19/12 2:34 AM, Christoph Maser wrote:
> Well the idea is to have additional saftey measures that check if
> the webapp is in the desired state after the context is started.
> This is done by sending queries against the webapp for stand
On 19 Apr 2012, at 08:07, "ma...@apache.org" wrote:
> Christoph Maser wrote:
>
>> 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,
Christoph Maser wrote:
>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 imp
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
> implementation. If there was a use
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph,
On 4/12/12 2:42 AM, Christoph Maser wrote:
> 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 reques
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
implementation. If there was a use case that wasn't completely off the wall
that couldn't be met then it would get l
Do you see any chance a request for feature in that direction would be
accpeted?
Chris
Am Donnerstag, den 12.04.2012, 09:40 +0100 schrieb Mark Thomas:
> The only control you have is by ensuring that the version you want to be used
> by default has the highest version number.
>
> Mark
>
> Chri
The only control you have is by ensuring that the version you want to be used
by default has the highest version number.
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
>a
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
16 matches
Mail list logo