[jboss-jira] [JBoss JIRA] (WFLY-2970) CLI doesn't return actual runtime configuration

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar reopened WFLY-2970:
-------------------------------

      Assignee: Richard Achmatowicz  (was: Alexey Loubyansky)


Sorry guys, looks like this was not fixed for jgroups mappings.
                
> CLI doesn't return actual runtime configuration
> -----------------------------------------------
>
>                 Key: WFLY-2970
>                 URL: https://issues.jboss.org/browse/WFLY-2970
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBoss AS7 7.1.1.Final
>            Reporter: Debbie Steigner
>            Assignee: Richard Achmatowicz
>
> If you start your server with -u commandline argument to bind your jgroups-udp to another IP (i.e. 230.0.0.13), the boot.log shows jboss.default.multicast.address = 230.0.0.13
> but if you read the resource via jboss-cli it shows just the default that is set in the standalone-ha.xml.  Is there a way to get the actual value via jboss-cli? or is this a bug?
> [standalone at 127.0.0.1:9999 /] /socket-binding-group=standard-sockets/socket-binding=jgroups-udp:read-resource(include-runtime=true)                         
> {
>     "outcome" => "success",
>     "result" => {
>         "bound" => false,
>         "bound-address" => undefined,
>         "bound-port" => undefined,
>         "client-mappings" => undefined,
>         "fixed-port" => false,
>         "interface" => undefined,
>         "multicast-address" => expression "${jboss.default.multicast.address:230.0.0.4}",
>         "multicast-port" => 45688,
>         "name" => "jgroups-udp",
>         "port" => 55200
>     }
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira