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

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-10748:
--------------------------------
    Summary: Changing multicast address in JGroups socket-binding does not trigger server to set reload-required  (was: Changing multicast address in socket binding does not trigger server to set reload-required)


> Changing multicast address in JGroups socket-binding does not trigger server to set reload-required
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10748
>                 URL: https://issues.jboss.org/browse/WFLY-10748
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 13.0.0.Final
>            Reporter: Paul Ferraro
>            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)