[HTTPASYNC-64] Race condition using CachingHttpAsyncClient

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0 Final
• Fix Version/s: 4.0.1
• Labels: CachingHttpAsyncClient FutureHttpResponse concurrency race-condition
• Environment: JDK 1.7, macbook pro
• Assignee: Unassigned
• Reporter: Rahul
• Created: 09/Jan/14 00:17
• Updated: 20/Feb/14 01:20
• Resolved: 27/Jan/14 14:29

Description

Running into a race condition when using CachingHttpAsyncClient. The async client at times returns null from the FutureHttpResponse obtained from CachingHttpAsyncClient.execute(HttpGet, null)

In FutureHttpResponse the get() method has the following implementation -
try

{ getDelegate().get(); }

catch (ExecutionException e)

{ // ignore }

final HttpResponse result = getResponse();

When the getDelegate().get(); returns, the getResponse() returns null. It seems the thread doing the actual request/response processing still hasn't called "setResponse".