You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jasper Rosenberg (JIRA)" <ji...@apache.org> on 2014/02/04 04:12:08 UTC

[jira] [Commented] (HTTPCLIENT-1453) PoolingHttpClientConnectionManager thread safety

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890323#comment-13890323 ] 

Jasper Rosenberg commented on HTTPCLIENT-1453:
----------------------------------------------

I have seen the same issue calling PoolingHttpClientConnectionManager.closeIdleConnections().  Given that it also ends up calling org.apache.http.pool.AbstractConnPool.purgePoolMap(AbstractConnPool.java:469), I'm assuming this is handled as well?  Thanks.


Caused by: java.util.ConcurrentModificationException
       at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926)
       at java.util.HashMap$EntryIterator.next(HashMap.java:966)
       at java.util.HashMap$EntryIterator.next(HashMap.java:964)
       at org.apache.http.pool.AbstractConnPool.purgePoolMap(AbstractConnPool.java:469)
       at org.apache.http.pool.AbstractConnPool.closeIdle(AbstractConnPool.java:500)
       at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.closeIdleConnections(PoolingHttpClientConnectionManager.java:358)


> PoolingHttpClientConnectionManager thread safety
> ------------------------------------------------
>
>                 Key: HTTPCLIENT-1453
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1453
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpConn
>    Affects Versions: 4.3.2
>         Environment: Windows 8.1 x64
> java version "1.7.0_45"
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>            Reporter: Rahim Alizada
>             Fix For: 4.3.3
>
>
> Although the PoolingHttpClientConnectionManager is marked as ThreadSafe, connectionManager.closeExpiredConnections() call from multiple threads causes ConcurrentModificationException.
> java.util.ConcurrentModificationException
> 	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:839)
> 	at java.util.HashMap$EntryIterator.next(HashMap.java:880)
> 	at java.util.HashMap$EntryIterator.next(HashMap.java:878)
> 	at org.apache.http.pool.AbstractConnPool.purgePoolMap(AbstractConnPool.java:469)
> 	at org.apache.http.pool.AbstractConnPool.closeExpired(AbstractConnPool.java:517)
> 	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.closeExpiredConnections(PoolingHttpClientConnectionManager.java:363)
> 	at com.jyvee.shared.http.HttpHelper.getHttpClient(HttpHelper.java:121)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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