You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2013/10/11 22:08:42 UTC
[jira] [Resolved] (HTTPCORE-355) HttpAsyncRequestExecutor fails
when its handler is not ready to generateRequest
[ https://issues.apache.org/jira/browse/HTTPCORE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCORE-355.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.3.1
You are absolutely correct.
Fixed in SVN trunk. Please review / re-test.
Oleg
> HttpAsyncRequestExecutor fails when its handler is not ready to generateRequest
> --------------------------------------------------------------------------------
>
> Key: HTTPCORE-355
> URL: https://issues.apache.org/jira/browse/HTTPCORE-355
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.3
> Environment: All
> Reporter: jd
> Fix For: 4.3.1
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> HttpAsyncRequestExecutor.requestReady incorrectly attempts to process a null HTTPRequest returned by HttpAsyncClientExchangeHandler.generateRequest when HttpAsyncClientExchangeHandler is not ready to do so. Instead, it should return back and let DefaultNHttpClientConnection.produceOutput clear WRITE, thereby allowing HttpAsyncClientExchangeHandler to wait generating the request when it is indeed ready to do so.
> This is necessary for usecases when there are more than one connections involved and it is necessary to block this connection until data becomes available on other.
> Refer Code: org.apache.http.nio.protocol.HttpAsyncRequestExecutor
> Line: 146, Add if (request == null) return;
> Version: httpcore-nio, 4.3
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org