Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2730

HTTP upgrade does not accept multiple acceptors

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 8.0.0.CR1
    • Fix Version/s: 8.0.0.Final
    • Component/s: JMS
    • Labels:
      None

      Description

      The http-acceptors are multiplexed over the HTTP port.
      If there are multiple http-acceptors registered, a http-connector that uses the HTTP upgrade mechanism will use the first whose handshake is successful and can not chose a given http-acceptor.
      With native messaging ports, the solution was to use different ports for different acceptors but with HTTP upgrade, everything goes through the HTTP port.

      HornetQ connectors must pass "http-upgrade-endpoint" when the HTTP upgrade is initiated so that we ensure the handshake is successful only for the matching acceptor corresponding to the "http-upgrade-endpoint" value.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  jmesnil Jeff Mesnil
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: