[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-5822: ------------------------------------------- The other possibility which Rado raised is that even though a session may be created on a node, the joining and leaving of nodes may change the primary, backup and non-owner status of nodes for a given session. This may result in a node which was formerly an owner of the session having to do a remote get each time it needs access to the session. The strong and weak affinity at the EJBClient level would be based on whether or not the node on which the session was initially created was still available to accept EJB client invocations. If the owner went down, the EJBClient would select another available node to direct invocations to, but this might not correspond to the new primary which Infinispan decided for the session. -- This message was sent by Atlassian JIRA (v6.4.11#64026)