[HTTPCLIENT-1453] PoolingHttpClientConnectionManager thread safety

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.2
• Fix Version/s: 4.3.3
• Component/s: HttpClient (classic)
• 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)
• Assignee: Unassigned
• Reporter: Rahim Alizada
• Created: 24/Jan/14 16:08
• Updated: 04/May/17 09:48
• Resolved: 19/Feb/14 11:13

Description

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)