[
https://issues.apache.org/jira/browse/HTTPCORE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506998#comment-14506998
]
Anders Jönsson commented on HTTPCORE-399:
-----------------------------------------
One way to investigate this is to put breakpoints in:
PipeliningClientExchangeHandlerImpl.requestCompleted()
and
PipeliningClientExchangeHandlerImpl.responseCompleted()
They will be visited in the following order:
requestCompleted
requestCompleted
responseCompleted
responseCompleted
and then (forever):
requestCompleted
responseCompleted
requestCompleted
responseCompleted
///Anders
> Http Pipelining is limited to two (2) requests, then acts synchronous.
> ----------------------------------------------------------------------
>
> Key: HTTPCORE-399
> URL: https://issues.apache.org/jira/browse/HTTPCORE-399
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Affects Versions: 4.4.1
> 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]
