hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPCORE-362) Memory leak in rout key of AbstractConnPool's routeToPool
Date Thu, 21 Nov 2013 14:09:41 GMT

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

Oleg Kalnichevski resolved HTTPCORE-362.

       Resolution: Fixed
    Fix Version/s: 4.3.1

Len (I hope I got your first name right)

I ended up committing a different, more conservative fix [1]. Pool per route map will get
purged only as a result of #closeExpired and #closeIdle. Empty pools will not get purged upon
connection release, as it may cause unnecessary intermediate garbage.

Your app will need to manually invoke #closeExpired during a long web crawl. 


[1] http://svn.apache.org/r1544185

> 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
>             Fix For: 4.3.1
>         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

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

View raw message