You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2013/11/21 11:30:38 UTC

[jira] [Updated] (HTTPCORE-362) Memory leak in rout key of AbstractConnPool's routeToPool

     [ https://issues.apache.org/jira/browse/HTTPCORE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski updated HTTPCORE-362:
---------------------------------------

    Attachment: HTTPCORE-362.patch

I am not sure I agree with this being a memory leak and am not sure that immediate removal of empty RouteSpecificPool entries is a good thing in all scenarios. I understand though that in the context of large web crawls involving thousands of sites that are never supposed to be crawled more than once this can present a problem. Could you please try out this patch and let me know if that solves the problem for you?

Oleg

> Memory leak in rout key of AbstractConnPool's routeToPool 
> ----------------------------------------------------------
>
>                 Key: HTTPCORE-362
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-362
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>            Reporter: len.liu
>         Attachments: HTTPCORE-362.patch
>
>
> routeToPool which is a map,could not  release any route key anytime, it only releases value object based on the setting number of 'maxTotal' and 'MaxPerRoute',  so the routeToPool(exactly the route keys), will use larger and larger memory util JVM is out of memory.
> This problem will happened when requesting lots of different  HttpHost.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org