dev@grizzly.java.net

Re: cached buffer's order problem

From: Ryan Lubke <ryan.lubke_at_oracle.com>
Date: Thu, 07 Feb 2013 08:37:50 -0800

Thanks Bongjae, we'll get this applied today.

> Bongjae Chang <mailto:bongjae.chang_at_gmail.com>
> February 7, 2013 3:35 AM
> Hi,
>
> When I used a custom filter and AJP13 filter, I met some problems(some
> AJP13 request/response was blocked) so I debugged mod_jk and
> grizzly-http-ajp modules.
> The problem was caused by reused buffer's byte order.
>
> My custom filter used the buffer with little endian order(I set
> Buffer#order(ByteOrder.LITTLE_ENDIAN)).
> And the buffer and buffer's order also reused in AJP13 filter because
> the buffer was cached(released) without resetting the byte order when
> it was disposed. But AJP13 or most of filter assume that buffer's
> order is big endian.
>
> So, I think the buffer's order should be also cleared with default
> when it is disposed and cached.
>
> I attached the proposed patch based on 2.2.x.
>
> Thanks!
>
> Regards,
> Bongjae Chang
>