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

Support one-port connection for JMS

    Details

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

      Description

      WildFly 8 needs to support one-port where all the remote connections goes through HTTP with Upgrade header.
      A JMS client will be able to connect to WildFly's HTTP port to access its JMS resources instead of connecting to the TCP socket on HornetQ remote port (5445).

        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: