[
https://issues.apache.org/jira/browse/AMQ-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893664#comment-16893664
]
ASF subversion and git services commented on AMQ-6397:
------------------------------------------------------
Commit 8e8041c69aaf1bcc99d352c777c248b6d5c6d0c5 in activemq's branch
refs/heads/activemq-5.15.x from suem
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8e8041c ]
AMQ-6949: SocketTimeoutException when using HTTP transport connector
A default socket timeout of 30 secods for the HTTP client was introduced with
the following ticket: https://issues.apache.org/jira/browse/AMQ-6397
This timeout somewhow seems to conflict with the keep alive requests that stays
open for arround 30 seconds. I increased the default timeout to 90 seconds and
this seems to resolve the problem.
> 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
> Priority: Major
> 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
(v7.6.14#76016)
