Another thought to consider: a redirect does not stop processing on the
current request. If you call a redirect in a filter and don't return
immediately, this condition can occur.
--David
Greg Ward wrote:
On 03 October 2006, Dan Adams said:
Hmm, I don't think that is the culprit. I thi
On 03 October 2006, Dan Adams said:
> Hmm, I don't think that is the culprit. I think all of our stuff is
> thread safe. We're using a framework (Tapestry) which shields us from
> threading issues like that and prevents us from storing request stuff in
> the session. Also, if that were the case wou
Hmm, I don't think that is the culprit. I think all of our stuff is
thread safe. We're using a framework (Tapestry) which shields us from
threading issues like that and prevents us from storing request stuff in
the session. Also, if that were the case would that cause problems when
loading static f
> From: Dan Adams [mailto:[EMAIL PROTECTED]
> Subject: Response already committed
>
> I'm getting a problem that appears to occur randomly. If I request the
> same page in my webapp over and over most of the time it will come up
> fine but sometimes tomcat won't return anything and I'll get a bla
David C. Schweisguth <[EMAIL PROTECTED]> wrote:
>
> Mar 2, 2006 2:15:47 PM org.apache.jk.core.MsgContext action
> INFO: Response already committed
I have a lot of these every single mintue, and
I'm not redirecting any error pages, just making
a header location stuff. See my recent posts.
--
T.
"David C. Schweisguth" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi all,
>
> I'm using Apache 2.something, mod_jk and Tomcat 5.5.15. mod_jk sends all
> requests to Tomcat, so Tomcat needs to handle requests for nonexistent
> paths. Our application handles requests to more th
