[
https://issues.apache.org/jira/browse/AMQ-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424527#comment-15424527
]
ASF subversion and git services commented on AMQ-6397:
------------------------------------------------------
Commit 124bd1ae3d1f015b2e605288e624ecf2f921c67f in activemq's branch
refs/heads/activemq-5.14.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=124bd1a ]
https://issues.apache.org/jira/browse/AMQ-6397
Setting the HTTP timeout for all HttpClients instead of just on send
(cherry picked from commit 06e929f1016571f9e5a024e42a4fc5298d9f9684)
> Configure HTTP timeouts in HttpClientTransport for receive in addition to send
> ------------------------------------------------------------------------------
>
> Key: AMQ-6397
> URL: https://issues.apache.org/jira/browse/AMQ-6397
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.11.0, 5.14.0
> Reporter: Nate Klein
> Assignee: Christopher L. Shannon
> Fix For: 5.14.1, 5.15.0
>
> Attachments: patchfile.txt
>
>
> We've experienced a situation where when creating a connection, the thread is
> stuck in a socket read during the HTTP HEAD call to the broker from
> HttpClientTransport:
> {code}
> httpClient.execute(httpMethod, new BasicResponseHandler());
> {code}
> After reading through the usage of HttpClient, it looks as though soTimeout
> is only set on the sent HttpClient instances, not the receive. This patch
> adds the timeout to both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
