[jboss-jira] [JBoss JIRA] (WFCORE-3977) Changing multicast address in socket binding does not trigger server to set reload-required
[
https://issues.jboss.org/browse/WFCORE-3977?page=com.atlassian.jira.plugi...
]
Radoslav Husar commented on WFCORE-3977:
----------------------------------------
This should work like other services work, if its service is up it should be put in
reload-required state.
Checking the service, it is actually up (jgroups subsystem configuration builders add the
dependency):
{noformat}
Service \"org.wildfly.network.socket-binding.jgroups-mping\" (aliases:
jboss.binding.jgroups-mping) (class org.jboss.as.server.services.net.SocketBindingService)
mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies:
org.wildfly.network.interface.pr
ivate, org.wildfly.management.socket-binding-manager)
{noformat}
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)