users@grizzly.java.net

GrizzlyResponse object reachable from SelectorRunner thread local

From: Rodrigo Merino <rodrigo.merino_at_mulesoft.com>
Date: Mon, 21 Dec 2015 17:24:23 -0300

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:

[image: 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>



image.png
(image/png attachment: image.png)