[
https://issues.apache.org/jira/browse/HTTPCORE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192528#comment-13192528
]
Oleg Kalnichevski commented on HTTPCORE-291:
--------------------------------------------
All right. I also do not want to delay the release unnecessarily as it blocks
releases of HttpClient and HttpAsyncClient. I'll see if full support for
pipelined request could be added in the course of BETA2 development.
Feel free to re-test your application against the release candidate and let me
know immediately if anything does not work as intended.
https://svn.apache.org/repos/asf/httpcomponents/httpcore/tags/4.2-beta1-RC2/
Oleg
> Out-of-order responses to pipelined requests
> --------------------------------------------
>
> Key: HTTPCORE-291
> URL: https://issues.apache.org/jira/browse/HTTPCORE-291
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Reporter: Geir Harald Hansen
> Attachments: Test.java, testrun.txt
>
>
> I am having a problem with the latest HttpCore NIO from the Subversion
> repository (revision 1234228). I have not tested this on earlier versions.
> I am observing two problems, but they stem from the same underlying issue -
> that after a response is delayed, processing of subsequent pipelined requests
> on the same socket continues immediately.
> Problem 1: If the response to your first request is delayed, but not the
> second, they are delivered out of order.
> Problem 2: If a request has a body (entity) then right after processing that
> request and delaying its response, there is a response on the wire ("400 Bad
> Request") and the connection is terminated. When this happens none of the
> delayed responses are cancelled, that is Cancellable#cancel() is never called.
> I will attach example source code, and an example of running telnet against
> the program, to show what is happening. There is first a request that is
> delayed and never gets a response. The second request gets a response
> immediately, out of order. The third request (a POST with body) also has its
> response delayed. But then there is a 400 bad request response and the
> connection is severed. The two delayed responses are not cancelled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
