users@grizzly.java.net

Re: GrizzlyResponse object reachable from SelectorRunner thread local

From: Oleksiy Stashok <oleksiy.stashok_at_oracle.com>
Date: Mon, 21 Dec 2015 12:34:35 -0800

Hi Rodro,

could you pls. create an issue and link the testcase, so we can look
into that?

Thanks.

WBR,
Alexey.

On 12/21/15 12:24 PM, Rodrigo Merino wrote:
> Hi,
>
> We are using grizzly (version 2.3.21) to perform some HTTP requests.
> After those requests have finished, in a thread dump i can still see
> the response objects being referenced, and not being garbage
> collected. Attached is a screenshot of there references from a heap dump:
>
> Inline image 1
> In a case where the size of the transferred data is big, i see some
> heavy memory usage.
>
> Question is, are those references held on purpose and would be removed
> eventually as the application runs or is this a bug that could
> potentially cause a memory leak? In any way, i would expect these
> objects to not be held by the connection once the http transfer has
> finished.
>
> Thanks in advance,
> Rodro
>
>
> --
> <http://www.mulesoft.com/>
>
>
> Rodrigo Merino, ESB Developer
> Av. Corrientes 316 Entre Piso, Buenos Aires, C1
> <http://alligatorcreek.s3-us-west-2.amazonaws.com/email-signature.html#>043AAQ,
> Argentina
>
> <https://www.linkedin.com/company/www.mulesoft.com>
> <https://twitter.com/mulesoft> <https://www.facebook.com/MuleSoft>
> <https://www.youtube.com/user/mulesoftvids> We're hiring!
> <http://www.mulesoft.com/careers>
>