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

Fix resolution of getHubHost and getHubPort in GridNodeConfiguration. #5219

Closed
kool79 opened this issue Dec 13, 2017 · 0 comments
Closed

Fix resolution of getHubHost and getHubPort in GridNodeConfiguration. #5219

kool79 opened this issue Dec 13, 2017 · 0 comments
Labels

Comments

@kool79
Copy link
Contributor

kool79 commented Dec 13, 2017

There are several related issues:

issue 1:

As documented here the hub parameter should take precedence over -hubHost and -hubPort.
But actually parameter -hubHost and -hubPort have higher priority when both params defined.

issue 2:

When one of the hubHost or hubPort is equal to null then result returned by getHubPort() and getHubHost() can depend on invocation order:

Precondition:

hub: "http://hostA:1111"
hubHost: "hostB"
hubPort: null

step 1: call to getHubHost() returns "hostB" (from hubHost parameter)
step 2: call to getHubPort() returns 1111 (from hub parameter)
step 3: repeat call to getHubHost() - now it returns "hostA" (from hub parameter)

@lock lock bot locked and limited conversation to collaborators Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants