You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/08/17 13:38:20 UTC
[jira] [Resolved] (AMQ-6397) Configure HTTP timeouts in
HttpClientTransport for receive in addition to send
[ https://issues.apache.org/jira/browse/AMQ-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon resolved AMQ-6397.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.15.0
Thanks for the patch, I have applied it to master.
> 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.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)