[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=13611213#comment-13611213 ] 

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

[~pferraro] So the ON_DEMAND socket binding service is UP even though Service<TransportConfiguration> is DOWN?

If it's not UP the service would be reinstalled with the current config.

I haven't thought hard about it (I'll leave that to others ;) ) but I can see how the 'bound' check might be more trouble than it's worth. But it seems like a piece is missing somewhere for this particular case.

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