Craig,
Thanks for your prompt reply, and sorry for my delayed reply (I was out
of the office yesterday).
> * Do you have a small test case we can use to investigate this?
> If so, you can send it either to TOMCAT-DEV or to me in private
mail.
A .war file containing an example is attached to t
Quoting "Craig R. McClanahan" <[EMAIL PROTECTED]>:
> On Wed, 30 May 2001, Craig R. McClanahan wrote:
>
> > Hello Paul,
> >
> > This definitely sounds like something wrong with Tomcat 4 -- most
> likely a
> > combination of things related to the browser (which can affect which
> HTTP
> > version
its certainly in excess of a
> > minute).
> >
> > When using a WAP 'phone, the 'phone times out with an error.
> >
> > The problem only occurs if I use my filter on a JSP file. It does not
> > occur when the filter is used on a "plain" HTML fil
y occurs if I use my filter on a JSP file. It does not
> occur when the filter is used on a "plain" HTML file.
>
> If there are any more details that I can provide, please let me know and
> I'll do my best.
>
> Thanks,
>
> pbutcher->msgCount++
>
>
If there are any more details that I can provide, please let me know and
I'll do my best.
Thanks,
pbutcher->msgCount++
--
Team Leader, Argogroup plc
http://www.argogroup.com/
>From: "Kevin Jones" <[EMAIL PROTECTED]>
>Date: Wed, 31 Jan 2001 20:27:34 - >To:
&
; To: [EMAIL PROTECTED]
> Subject: Re: Filter Chains slow first time it is called
>
>
> Kevin Jones wrote:
>
> > Subject says it all really.
> >
> > The first time a filter chain is executed for a servlet, it
> takes about 30
> > seconds for the response
Kevin Jones wrote:
> Subject says it all really.
>
> The first time a filter chain is executed for a servlet, it takes about 30
> seconds for the response to get back to the client.
>
It would be surprising if this is related to initializing the filter chain --
after all, the chain is constructe
Subject says it all really.
The first time a filter chain is executed for a servlet, it takes about 30
seconds for the response to get back to the client.
This doesn't happen everytime but enough to be repeatable.
I'm using Beta 1. I've set the app to be reloadable (with a reload time of
3) and
