Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10493

It is possible to add multiple http-connectors to the same undertow listener

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.0.CD12
    • 7.1.0.DR16
    • Remoting, Undertow
    • None

    Description

      User can add multiple http-connector s with the same socket binding:

      [standalone@localhost:9990 /] /subsystem=remoting/http-connector=http-remoting-connector1:add(connector-ref=default, sasl-authentication-factory=application-sasl-authentication)
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=remoting/http-connector=http-remoting-connector2:add(connector-ref=default, sasl-authentication-factory=application-sasl-authentication)
{"outcome" => "success"}

      This is not possible with connector:

      [standalone@localhost:9990 /] /subsystem=remoting/connector=dup1:add(sasl-authentication-factory=application-sasl-authentication, socket-binding=dup)
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=remoting/connector=dup2:add(sasl-authentication-factory=application-sasl-authentication, socket-binding=dup)
{
    "outcome" => "failed",
    "failure-description" => \{"WFLYCTL0080: Failed services" => \{"jboss.remoting.server.dup2" => "WFLYRMT0004: Address already in use 127.0.0.1:12345
    Caused by: java.net.BindException: Address already in use"}},
    "rolled-back" => true
}

      The preferred behaviour should be consistent with connector - it makes no sense to have multiple connectors for single port as the client applications do not distinguish connectors by anything else than ports.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3286 It is possible to add multiple http-connectors to the same undertow listener

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12932 Upgrade WildFly Core to 4.0.1.Final

          • 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

              jondruse@redhat.com Jiri Ondrusek
              mjurc@redhat.com Michal Jurc
              Richard Janik Richard Janik
              Richard Janik Richard Janik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: