[jboss-jira] [JBoss JIRA] (WFLY-6832) Subsystem - connector resource description and schema file claim that more socket bindings can be used

[Chao Wang (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Wang moved JBEAP-5191 to WFLY-6832:
----------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-6832  (was: JBEAP-5191)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Remoting
                           (was: CLI)
                           (was: Remoting)
    Affects Version/s: 10.0.0.Final
                           (was: 7.0.0.GA)


> Subsystem - connector resource description and schema file claim that more socket bindings can be used
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-6832
>                 URL: https://issues.jboss.org/browse/WFLY-6832
>             Project: WildFly
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 10.0.0.Final
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>
> Since the schema for Remoting subsystem says that multiple socket bindings should be allowed on a connector, I'm trying to create a connector like that and I couldn't get it to work.
> I assume the correct syntax should be the one with {{[rjanik-sb1,rjanik-sb2]}} since the socket bindings are defined as {{xs:list}} in the schema file. Here's what I tried:
> {code}
> [standalone at localhost:9990 /] /socket-binding-group=standard-sockets/socket-binding=rjanik-sb1:add(interface=public)
> {"outcome" => "success"}
> [standalone at localhost:9990 /] /socket-binding-group=standard-sockets/socket-binding=rjanik-sb2:add(interface=public)
> {"outcome" => "success"}
> standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="rjanik-sb1 rjanik-sb2")
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: Invalid name character at offset 45",
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="rjanik-sb1, rjanik-sb2")
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: Invalid name character at offset 46",
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="rjanik-sb1,rjanik-sb2")
> {
>     "outcome" => "failed",
>     "failure-description" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.newcon is missing [org.wildfly.network.socket-binding.rjanik-sb1,rjanik-sb2]"]},
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="org.wildfly.network.socket-binding.rjanik-sb1,org.wildfly.network.socket-binding.rjanik-sb2")
> {
>     "outcome" => "failed",
>     "failure-description" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.newcon is missing [org.wildfly.network.socket-binding.org.wildfly.network.socket-binding.rjanik-sb1,org.wildfly.network.socket-binding.rjanik-sb2]"]},
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="rjanik-sb1,org.wildfly.network.socket-binding.rjanik-sb2")
> {
>     "outcome" => "failed",
>     "failure-description" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.newcon is missing [org.wildfly.network.socket-binding.rjanik-sb1,org.wildfly.network.socket-binding.rjanik-sb2]"]},
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding=[rjanik-sb1,rjanik-sb2])
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0097: Wrong type for socket-binding. Expected [STRING] but was LIST",
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="[rjanik-sb1,rjanik-sb2]")
> {
>     "outcome" => "failed",
>     "failure-description" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.newcon is missing [org.wildfly.network.socket-binding.[rjanik-sb1,rjanik-sb2]]"]},
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding="[rjanik-sb1],[rjanik-sb2]")
> {
>     "outcome" => "failed",
>     "failure-description" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.newcon is missing [org.wildfly.network.socket-binding.[rjanik-sb1],[rjanik-sb2]]"]},
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=remoting/connector=newcon:add(socket-binding=["rjanik-sb1","rjanik-sb2"])
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0097: Wrong type for socket-binding. Expected [STRING] but was LIST",
>     "rolled-back" => true
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)