[jboss-jira] [JBoss JIRA] (AS7-5334) JGroups protocol properties not always being applied to protocol configurations
[
https://issues.jboss.org/browse/AS7-5334?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro commented on AS7-5334:
-----------------------------------
The description is misleading...
It's not that the protocol properties are not being applied to the generated jgroups
channels - it's that these properties are not represented in the
export-native-configuration operation output. Socket bindings are applied to the protocol
stack during channel creation. Since the current implementation of
export-native-configuration operates off of the protocol stack configuration, it does not
properly include these properties. I suggest modifying the implementation of this
operation such that it creates a new channel using the ChannelFactory (without connecting
it) and outputs the relevant xml.
JGroups protocol properties not always being applied to protocol
configurations
--------------------------------------------------------------------------------
Key: AS7-5334
URL: https://issues.jboss.org/browse/AS7-5334
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.2.Final (EAP)
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 7.1.3.Final (EAP)
In JGroups subsystem processing, JGroups protocol properties are updated correctly in the
model but not always correctly applied to the runtime configuration.
For example, specifying an MPING.mcast_port as a property of the protocol MPING will be
overridden by the value of the multicast port in the associated socket binding.
--
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