[
https://issues.apache.org/jira/browse/HTTPCLIENT-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-1453:
------------------------------------------
Fix Version/s: 4.3.3
This is a know issue. Until the next release you can work it around by
upgrading HttpCore to the latest 4.3.2-SNAPSHOT.
Oleg
> 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: [email protected]
For additional commands, e-mail: [email protected]
