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

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-3977:
------------------------------------------

It's not just whether the service is up.

{code}
        final SocketBinding binding = controller.getState() == ServiceController.State.UP ? SocketBinding.class.cast(controller.getValue()) : null;
        final boolean bound = binding != null && binding.isBound();
{code}

The value of 'bound' controls whether reload-required is set.  Whether it reports as bound is controlled by the SocketBindingManager

> 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)