It is possible to add multiple http-connectors to the same undertow listener ---------------------------------------------------------------------------- Key: WFCORE-3286 URL: https://issues.jboss.org/browse/WFCORE-3286 Project: WildFly Core Issue Type: Bug Components: Remoting Affects Versions: 3.0.1.Final Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek User can add multiple {{http-connector}} s with the same socket binding: {code}[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"}{code} This is not possible with {{connector}}: {code}[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 } {code} 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.