[
https://issues.apache.org/jira/browse/HTTPASYNC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506925#comment-14506925
]
Anders Jönsson commented on HTTPASYNC-91:
-----------------------------------------
Yes, I'm pretty sure that this response pattern is a result of some kind of
problem in the pipelining code.
I am fully aware that this is a "valid" pipelined response, but I have run a
variety of tests across different environments and the result is always the
same. There are ALWAYS two requests followed by two responses, without any
exception. After that all the following requests are ALWAYS immediately
followed by a response before the next request is sent. I have watched numerous
Wireshark traces to come to this conclusion.
Further info:
I am using the CloseableHttpPipeliningClient.
The call I do looks like this:
Future<List<HttpPipelineResponse>> future = getHttpClient().execute(targetHost,
requestProducers, responseConsumers, responseCallbacks);
///Anders
> Http Pipelining is limited to two (2) requests, then acts synchronous.
> ----------------------------------------------------------------------
>
> Key: HTTPASYNC-91
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-91
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1-beta1
> Reporter: Anders Jönsson
> Labels: HttpAsyncClient, HttpPipelining
>
> When issuing pipelined (list of) http requests only the two first requests
> are actually sent in an asynchronous way. After the two first, all requests
> are sent synchronously, i.e. a response is awaited before sending the next
> request. Like this:
> Request ->
> Request ->
> ->Response
> ->Response
> Request ->
> ->Response
> Request ->
> ->Response
> etc.....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
