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

Support one-port connection for JMS

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Critical
    • 8.0.0.CR1
    • 8.0.0.Alpha4
    • JMS
    • 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).

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-2469 Upgrade to HornetQ 2.4.0.BETA3

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-206 Allow access to JMS destinations over HTTP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: