I've just added a comment as well based on my interpretation of the 3.0
Servlet spec. It looks like Grizzly is behaving according to the spec, but
I fail to see how I, as a user of the servlet API, can reliably avoid
"non-deterministic behavior" as a result of request/response recycling
since timeouts always cause the request to be completed. Honestly, unless
I'm missing something (which wouldn't be the first time ;-)), I suspect
that the Servlet API is broken w.r.t timeouts. What do you think?
Matt
On 3 September 2012 10:51, Matthew Swift <matthew.swift_at_gmail.com> wrote:
>
>
> On 31 August 2012 22:36, Ryan Lubke <ryan.lubke_at_oracle.com> wrote:
>
>>
>> We'll need to look into this for sure. Would you mind logging an issue
>> to keep track of this one?
>>
>
>
> No problem. Here it is: http://java.net/jira/browse/GRIZZLY-1325
>
> Matt
>
>