-
Bug
-
Resolution: Done
-
Major
-
None
-
None
This looks like a regression. Creating a server config from scratch by executing operations I see that the endpoint configuration has disappeared from the config although the add operation is executed. In fact I noticed that I can execute the add operations as many times as I want w/o an error. The config file is re-written after every add but the endpoint element is not added.
[standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=remoting/configuration=endpoint:add {"outcome" => "success"}
<subsystem xmlns="urn:jboss:domain:remoting:4.0"> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> </subsystem>
Note, that if I add a worker as a param, it will persist the endpoint config.
- is related to
-
WFCORE-3327 Confusion about the recording of the org.wildfly.remoting.endpoint capability and the resource that configures it
- Resolved