https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
Remy Maucherat changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #7 from Remy Maucherat ---
(In reply to Mark Thomas from comment #6)
> (In reply to Remy Maucherat from comment #4)
>
> > I think I will add a new asyncComplete method to allow processors to
> > do that kind of thing. I believe HTT
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #6 from Mark Thomas ---
(In reply to Remy Maucherat from comment #4)
> I think I will add a new asyncComplete method to allow processors to
> do that kind of thing. I believe HTTP/1.1 and AJP need to use it.
dispatchEndRequest() l
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #5 from Nagendra ---
If you are planning to address this issue in an upcoming patch, I’d be happy to
assist with testing. I’ve already reproduced the issue locally with Tomcat
setup and can help validate whether the fix ensures that
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
Remy Maucherat changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #4 from Remy Mauchera
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #3 from Nagendra ---
When a request is processed synchronously, Tomcat works fine as follows.
1. Handles the request and sends a response.
2. Waits for the next request from the same client for a duration defined by
keepAliveTimeou
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
--- Comment #2 from Remy Maucherat ---
The keep alive you are thinking about probably does not apply to async. Async
is a single request (and it uses its own timeout usually), while keep alive is
the amount of time a connection stays open betwe
https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
Christopher Schultz changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #1 from Chr
