You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2017/01/20 14:53:26 UTC
[jira] [Updated] (ARTEMIS-931) Improve HTTP upgrade connection
[ https://issues.apache.org/jira/browse/ARTEMIS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic updated ARTEMIS-931:
------------------------------------
Fix Version/s: 1.5.x
2.0.0
> Improve HTTP upgrade connection
> -------------------------------
>
> Key: ARTEMIS-931
> URL: https://issues.apache.org/jira/browse/ARTEMIS-931
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.2
> Reporter: Jeff Mesnil
> Fix For: 2.0.0, 1.5.x
>
>
> When Artemis connector is configured to use http-upgrade, it will send an HTTP request to the server to perform the upgrade handshake and wait for response for 30 seconds maximum.
> The code in HttpUpgradeHandler#channelRead0 checks if the received object from the server is a HttpResponse and check its header.
> However if the received object is not an HttpResponse (e.g. a LastHttpContent if the web server is suspended and returns a 404 with a text content), the code does not close the context and does not countdown the latch.
> This results in a 30s block for the client when we already know that the connection will not be possible.
> Improving code in HttpUpgradeHandler#channelRead0 will remove this 30s wait time and ensure a fast dectection from the client so that it can try to connect to another server for example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)