Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EJBCLIENT-132] Prevent ClusterNodeSelector from selecting connected nodes which do not satisfy the EJBLocator. #114

Merged
merged 1 commit into from
Apr 30, 2015

Conversation

rachmatowicz
Copy link
Contributor

This PR is a revision of the original PR for EJBCLIENT-132.

This change does the following:

  • it avoids the problem with restart of nodes in a cluster (mentioned in the issue) by preventing the ClusterNodeSelector from selecting an available,connected node from the cluster context which does not have module availability for the EJBLocator of the current invocation
  • it also does not interfere with the policy of removing per-invocation excluded nodes from the cluster context, which was what caused the problems with the original fix for EJBCLIENT-132

@rachmatowicz
Copy link
Contributor Author

Still waiting to confirm results of the SmartFrog performance test with this fix. Should be ready in the next day.

@wildfly-ci
Copy link

Build 69 is now running using a merge of 18c52b4

@wildfly-ci
Copy link

Build 69 outcome was SUCCESS using a merge of 18c52b4
Summary: Tests passed: 51 Build time: 0:00:39

@dmlloyd dmlloyd merged commit 18c52b4 into wildfly:1.0 Apr 30, 2015
dmlloyd added a commit that referenced this pull request Apr 30, 2015
[EJBCLIENT-132] Prevent ClusterNodeSelector from selecting connected nodes which do not satisfy the EJBLocator.
@rachmatowicz rachmatowicz deleted the EJBCLIENT-132-new branch July 14, 2015 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants