[
https://issues.jboss.org/browse/AS7-4095?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro updated AS7-4095:
------------------------------
Fix Version/s: 7.1.1.Final
Priority: Critical (was: Major)
Affects Version/s: No Release
(was: 7.1.1.Final)
Component/s: Clustering
This issue is bigger than just the multicast-port.
None of the configuration properties are getting picked up.
I'm bumping the priority.
mod_cluster AdvertiseListenerImpl does not take multicast-port
setting into account
-----------------------------------------------------------------------------------
Key: AS7-4095
URL:
https://issues.jboss.org/browse/AS7-4095
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: No Release
Reporter: Michal Babacek
Assignee: Tomaz Cerar
Priority: Critical
Labels: eap6_need_triage
Fix For: 7.1.1.Final
The undermentioned configuration with the current *master*
*{color:green}89daec9{color}*:
{code:lang=xml}
+++
<socket-binding-group name="standard-sockets"
default-interface="public"
port-offset="${jboss.socket.binding.port-offset:0}">
+++
<socket-binding name="modcluster" port="0"
multicast-address="224.0.1.105" multicast-port="6666"/>
+++
</socket-binding-group>
+++
{code}
does not affect the actual port the mod_cluster is looking for advertisement:
{code}
05:11:22,295 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC
service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira