There is a possibility of starvation of one node in the cluster if connection creation time is substantial. We encountered this scenario in environment in which LDAP was used as a credential store:

1. During the invocation the connection is opened to a node (node1) that was configured in EJB client. The connection is established, EJB client channel is created and information about applications on node1 are provided to the client. Information about other nodes in the cluster are provided in the client.
2. During subsequent invocations the discovery runs as follows: node1 DiscoveryAttempt's code runs immediately (connection is already established) and adds a result to discovery queue. The result is accepted and cancellation process for all other DiscoveryAttempt starts. Cancellation happens before a connection to any other node is established - information about applications on other node is not provided to the client.

The above scenario repeats for all subsequent invocations and node1 is selected 100% times.