[
https://issues.jboss.org/browse/WFLY-7240?page=com.atlassian.jira.plugin....
]
Radoslav Husar updated WFLY-7240:
---------------------------------
Description:
One of the manifestation of the issue:
# start 2 nodes with SLSB with TUNNEL transport
# start both nodes creating 2 clusters (or partitions)
# start ejb client
# start GossipRouter and wait for merge
# ejb client keeps talking only to known node; never receives a topology update
This is because org.wildfly.clustering.server.registry.CacheRegistry#topologyChanged does
not handle cluster merges.
was:
One of the manifestation of the issue:
# start 2 nodes with SLSB with TUNNEL transport
# start both nodes creating 2 partitie
# start ejb client
# start GossipRouter and wait for merge
# ejb client keeps talking only to 1st node, never receives a topology update
This is because org.wildfly.clustering.server.registry.CacheRegistry#topologyChanged does
not handle cluster merges.
CacheRegistry is missing entries (e.g. client mappings) following a
merge
-------------------------------------------------------------------------
Key: WFLY-7240
URL:
https://issues.jboss.org/browse/WFLY-7240
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.Final, 10.1.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
One of the manifestation of the issue:
# start 2 nodes with SLSB with TUNNEL transport
# start both nodes creating 2 clusters (or partitions)
# start ejb client
# start GossipRouter and wait for merge
# ejb client keeps talking only to known node; never receives a topology update
This is because org.wildfly.clustering.server.registry.CacheRegistry#topologyChanged does
not handle cluster merges.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)