[ https://issues.jboss.org/browse/WFLY-9276?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz updated WFLY-9276: -------------------------------------- Description: Copied from JBEAP-12889: {quote} The EJB client relies on topology updates from servers in order to maintain a view of cluster membership. These updates are supplied with membership information by a replicated cache called the client-mappings cache. When a server starts up, it puts a client-mappings entry into this cache. When topology changes occur, the client mappings cache entries are consulted to build the topology update information. It has been observed that the number of entries in the client mappings cache on each node can vary, resulting in different views of the cluster topology being sent by different servers to the same client, resulting in an overall incorrect view of the cluster topology. Such incorrect views break load balancing. {quote} was: Copied from JBEAP-12889: {noformat} The EJB client relies on topology updates from servers in order to maintain a view of cluster membership. These updates are supplied with membership information by a replicated cache called the client-mappings cache. When a server starts up, it puts a client-mappings entry into this cache. When topology changes occur, the client mappings cache entries are consulted to build the topology update information. It has been observed that the number of entries in the client mappings cache on each node can vary, resulting in different views of the cluster topology being sent by different servers to the same client, resulting in an overall incorrect view of the cluster topology. Such incorrect views break load balancing. {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)