activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6397) Configure HTTP timeouts in HttpClientTransport for receive in addition to send
Date Wed, 17 Aug 2016 12:04:20 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424386#comment-15424386
] 

Christopher L. Shannon commented on AMQ-6397:
---------------------------------------------

This change makes sense as the value should apply to both sends/receives.  One thing I did
notice is that with this change the timeout period will now be cached permanently since it
will be set only once on the client creation which is then cached.  The way it is currently
constructed, the timeout is set on every send so in theory the timeout could be changed later
via the setter.  I don't really think this is an issue as the original intention was probably
to configure the setting once and not change it later.  What do you think [~tabish121] ?

> 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
>         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)

Mime
View raw message