[
https://issues.apache.org/jira/browse/HTTPASYNC-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986873#comment-14986873
]
Oleg Kalnichevski commented on HTTPASYNC-94:
--------------------------------------------
So, where is exactly the memory leak? The "available" LinkedLink contains
re-usable connections available for lease from the pool. It is its purpose. If
your pool is configured to have thousands connections and those connections use
SSL encryption one can easily end up with gigabytes of heap consumed by those
connections.
Olg
> LinkedList memory leak
> -----------------------
>
> Key: HTTPASYNC-94
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-94
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: httpclient 4.4
> httpcore 4.4
> httpcore-nio 4.4
> httpasyncclient 4.1
> Reporter: sunqi
>
> Class Name Shallow Heap Retained Heap
> java.util.LinkedList @ 0x750a89d08 32 3657440400
> org.apache.http.impl.nio.conn.CPool @ 0x750a86508 88 3764053968
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager @
> 0x751d65730 32 5640
> org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1 @
> 0x752621b08 24 24
> java.lang.Thread @ 0x751d470f8 pool-17-thread-1 104 5184
> org.apache.http.impl.nio.client.InternalHttpAsyncClient @ 0x7537dd778
> 72 88
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
