[
https://issues.redhat.com/browse/WFLY-9641?page=com.atlassian.jira.plugin...
]
Gregory Hall commented on WFLY-9641:
------------------------------------
I'm trying to cluster keycloak 6.0.1 based on Wildfly 16 in a docker container and
having this issue.
I've been setting external addresses on all the JGroups TCPPING protocol options.
Not sure what the best tactic as using 0.0.0.0 inside a container is definitely
preferred.
The basic pretense that the ejb cluster would second guess routability through an
inadequate test sounds wrong.
Due to NAT with/without docker containers and networks, the best practice would be to try
to connect and if you throw a NoRouteToHost, deal with that.
Cluster EJB can not work with "-b 0.0.0.0"
------------------------------------------
Key: WFLY-9641
URL:
https://issues.redhat.com/browse/WFLY-9641
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 11.0.0.Final
Reporter: Fred Ling
Priority: Major
Labels: cluster, ejb, wildfly
The ejb cluster does not work when bind to 0.0.0.0, using
--server-config=standalone-full-ha.xml -b 0.0.0.0.
The ejb client fails to connect to the cluster nodes because it tries to connect to
0.0.0.0.
For more information please refer to the forum thread.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)