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

[Paul Ferraro (JIRA)]

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

Paul Ferraro commented on WFCORE-3977:
--------------------------------------

[~brian.stansberry] In the case of JGroups, deferring restart of the Service<SocketBinding> until the socket is bound is too late.  JGroups contains services which depend on socket-bindings for their configuration.  They extract the address/port and configure the JGroups protocol accordingly.
Let's take the example of /subsystem=jgroups/transport=tcp...

This resource is configured with a socket-binding to which configures the TCP protocol with an InetAddress and port taken from the SocketBinding.  This service starts on-demand, when required by an associated channel.  In the "ha" profile, following startup of the server, the TCP protocol's Service<TransportConfiguration> will be DOWN (as no channel has forced it to start yet).
Now a user issues an update of the associated address/port of TCP's socket-binding.  The write-attribute operations will succeed, however, the corresponding Service<SocketBinding> will not restart, and the server is not put in reload-required, since this socket-binding is not bound (as you mentioned above).
Next a user deploys a distributed application, which starts a channel, and triggers the start of TCP's Service<TransportConfiguration>, however it will use outdated socket address/port values.

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