Rahul Biswas created HTTPASYNC-64:
-------------------------------------
Summary: Race condition using CachingHttpAsyncClient
Key: HTTPASYNC-64
URL: https://issues.apache.org/jira/browse/HTTPASYNC-64
Project: HttpComponents HttpAsyncClient
Issue Type: Bug
Affects Versions: 4.0 Final
Environment: JDK 1.7, macbook pro
Reporter: Rahul Biswas
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".
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
