https://bz.apache.org/bugzilla/show_bug.cgi?id=69748
Remy Maucherat <r...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #4 from Remy Maucherat <r...@apache.org> ---
(In reply to Nagendra from comment #3)
> Initial findings in the code
> -------------------------------
>
> Http11Processor.java - within the service method, synchronous request
> handling enters the while loop twice. The first iteration consumes the
> connectionTimeout value, and the second iteration consumes the
> keepAliveTimeout value via inputBuffer.parseRequestLine(). However, for
> asynchronous request handling, the loop runs only once due to the async flag
> condition, consuming only the connectionTimeout value and skipping the
> second iteration thereby ignoring the keepAliveTimeout.
It is normal that this exits Http11Processor.service, otherwise it would not be
async. However, there is nothing setting back the keepalive timeout after
processing AbstractProcessor.action->ASYNC_COMPLETE so it just stays like that.
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.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
