[jboss-jira] [JBoss JIRA] (WFLY-11806) socket-binding/jgroups-tcp client mappings do not map to jgroups.external_addr properly
[
https://issues.jboss.org/browse/WFLY-11806?page=com.atlassian.jira.plugin...
]
G. Richard Bellamy updated WFLY-11806:
--------------------------------------
Workaround Description:
The workaround is to pass in the required external address via the
{{jgroups.external_addr}} system property:
{code:title=option 1}
/system-property=jgroups.external_addr:add(value=${env.JGROUPS_NAME:external.host.zzz})
{code}
{code:title=option 2}
standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -bprivate 0.0.0.0
-Djgroups.external_addr=external.host.zzz
{code}
was:
The workaround is to pass in the required external address via the
{{jgroups.external_addr}} system property:
{code}
standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -bprivate 0.0.0.0
-Djgroups.external_addr=external.host.zzz
{code}
socket-binding/jgroups-tcp client mappings do not map to
jgroups.external_addr properly
---------------------------------------------------------------------------------------
Key: WFLY-11806
URL: https://issues.jboss.org/browse/WFLY-11806
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 15.0.1.Final
Reporter: G. Richard Bellamy
Assignee: Paul Ferraro
Priority: Major
Labels: JGroups
socket-binding/jgroups-tcp client mappings do not map to the system property
{{jgroups.external_addr}} correctly, and therefore jgroups ALWAYS advertises the address
bound to the {{private}} interface.
When setting the client mappings for the {{jgroups-tcp}} socket binding, wildfly should
ensure that the pingdata for various discovery protocols announces the destination address
set there, presumably by setting the {{jgroups.external_addr}} value.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)