Salut,
Richard Corsale wrote:
> I sent you an email off the list, better not to clutter up with this as it might be an issue with my code and not Grizzly.
OK thanks for the test (that's looks promising BTW :-)). The flushBuffer
is different. Mainly calling flushBuffer when a client closed the
connection in a look would never throw an IOException. Something like:
while(true)
res.flushBuffer();
Thread.sleep(5000) << Remote client close the connection
}
since the IOException was never thrown, the while(true) would have
looped forever, eating one thread. Pretty bad :-(
Now I'm looking at the your framework to see what's the issue.
A+
-- Jeanfrancois
>
> --Richard
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: users_at_grizzly.dev.java.net
> Sent: Wednesday, February 18, 2009 2:22:28 PM
> Subject: Re: 1.9.6 this week?
>
> Salut,
>
> Richard Corsale wrote:
>> I'm really interested in the issue with Grizzly Response, I noticed the other day that I would call flushbuffer() twice in rapid succession and it would send both payloads in the same flush. Is that the bug in 1.9.5 that were talking about?
>
> I still need a valid test case to reproduce the issue :-) I've never saw such issue, so if you can help that would be quite nice.
>
> Thanks
>
> -- Jeanfrancois
>
>
>> --Richard
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>