Jeff Mesnil created ARTEMIS-803:

             Summary: Do not offset port for http-upgrade acceptor for 
colocated backups
                 Key: ARTEMIS-803
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Broker
    Affects Versions: 1.4.0
            Reporter: Jeff Mesnil

In our application server, we use an embedded Artemis server with netty 
acceptors configured to enable HTTP Upgrade.
This means that the app server is using the HTTP port to negotiate a HTTP 
upgrade handshake with Artemis client. If the handshake is succesful, we 
transfer the connection from our HTTP handler to Artemis netty channel.

This causes issue with colocated backups as Artemis offsets all the ports for 
the Netty acceptor. If HTTP Upgrade is enabled, the port should not be offset 
(as it is "owned" by the app server).
Additionally, with colocated backups we have a single entry point (the app 
server's HTTP port) that can be used by multiple Artemis server (the main one 
and any of its colocated backups). When Artemis sends the HTTP request to 
initiate the upgrade, it should pass the name of the Artemis server that should 
handle the upgrade so that the app server can delegate the actual handshake to 
the correct Artemis server.

This message was sent by Atlassian JIRA

Reply via email to