Re: [5] Proposal: webapp startup

2002-08-20 Thread costinm
Aha ! I think I got it, it has nothing to do with the naming... When I do a start() and try to do the config in the background, the 'ok' return status is not set and the main thread believe an error happened and resets the resource field. Costin On Tue, 20 Aug 2002 [EMAIL PROTECTED] wrote:

Re: [5] Proposal: webapp startup

2002-08-20 Thread costinm
On Tue, 20 Aug 2002, Alex Chaffee / Purple Technology wrote: > There is a third option, by the way: > > 3. Wait with timeout. The request is queued, but if it takes longer > than a specified time to process (say, 20 seconds), then it returns a > 503. Probably that's the best - and should be th

Re: [5] Proposal: webapp startup

2002-08-20 Thread costinm
On Tue, 20 Aug 2002, Jean-francois Arcand wrote: > Actually, implementing the xml validation on/off mechanism, admin/ is > _the_ reason why Tomcat is slow at startup. There is a lot of xml files > to parse/validate in that applicationso I'm +1 to load on demand and > set validation to fals

Re: [5] Proposal: webapp startup

2002-08-20 Thread Alex Chaffee / Purple Technology
On Tue, Aug 20, 2002 at 09:59:11AM -0700, [EMAIL PROTECTED] wrote: > There are several possible use cases, and I think we should try to > provide options to support each one. Agreed. > Regardless of the startup timing, in all cases no request will > be served from an webapp until all initializa

Re: [5] Proposal: webapp startup

2002-08-20 Thread Remy Maucherat
Jean-francois Arcand wrote: > > > [EMAIL PROTECTED] wrote: > >> There are several possible use cases, and I think we should try to >> provide options to support each one. >> >> Regardless of the startup timing, in all cases no request will >> be served from an webapp until all initialization is

Re: [5] Proposal: webapp startup

2002-08-20 Thread Jean-francois Arcand
[EMAIL PROTECTED] wrote: >There are several possible use cases, and I think we should try to >provide options to support each one. > >Regardless of the startup timing, in all cases no request will >be served from an webapp until all initialization is done, including >load on startup servlets. T

[5] Proposal: webapp startup

2002-08-20 Thread costinm
There are several possible use cases, and I think we should try to provide options to support each one. Regardless of the startup timing, in all cases no request will be served from an webapp until all initialization is done, including load on startup servlets. There are 2 options here: 1. Wait.