[jboss-jira] [JBoss JIRA] (WFCORE-3977) Changing multicast address in socket binding does not trigger server to set reload-required

[Richard Achmatowicz (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610586#comment-13610586 ] 

Richard Achmatowicz commented on WFCORE-3977:
---------------------------------------------

Example: start a server:
{code}
[nrla at localhost bin]$ ./standalone.sh -c standalone-full-ha.xml
=========================================================================
  JBoss Bootstrap Environment
  JBOSS_HOME: /home/nrla/projects/wildfly-git-repo-new/dist/target/wildfly-14.0.0.Beta1-SNAPSHOT
  JAVA: /opt/jdk-1.8.0_121/bin/java
  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
11:27:56,856 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
11:27:57,065 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final

[snip]

11:28:02,824 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
11:28:02,825 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
11:28:02,825 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
11:28:02,825 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 14.0.0.Beta1-SNAPSHOT (WildFly Core 6.0.0.Alpha3) started in 6223ms - Started 447 of 641 services (407 services are lazy, passive or on-demand)
{code}

make the change in the console:

{code}
nrla at localhost bin]$ ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone at localhost:9990 /] /socket-binding-group=standard-sockets/socket-binding=jgroups-mping:write-attribute(name="multicast-address", value="230.0.0.9")
{"outcome" => "success"}
[standalone at localhost:9990 /] 
{code}


> Changing multicast address in socket binding does not trigger server to set reload-required
> -------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-3977
>                 URL: https://issues.jboss.org/browse/WFCORE-3977
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Management
>    Affects Versions: 6.0.0.Alpha3
>            Reporter: Richard Achmatowicz
>            Assignee: Jeff Mesnil
>
> Found this by accident when debugging a clustering test case.
> If I start a server with profile standalone-full-ha and then modify the multicast address of a clustering related socket-binding, in this case, jgroups-mping, the server is not put into state reload-required.
> This causes a lot of problems in the testsuite which depends on configuring servers after startup and then restarting if necessary to pull in the changes.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)