-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR16
-
None
-
User Experience
-
-
-
-
-
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.
- is cloned by
-
-
- Resolved
-
- is incorporated by
-
JBEAP-12932 Upgrade WildFly Core to 4.0.1.Final
-
- Closed
-