GitHub user sjcorbett opened a pull request:
https://github.com/apache/brooklyn-server/pull/497
Add findOpenSocketsOnNode to ReachableSocketFinder
This changes the semantics of ReachableSocketFinder. Previously it would
return as soon as any host+port was reached. Now it determines the status of
each socket in order. The checks are concurrent but, for example, if the third
of five sockets is reachable the status of the first and second will also be
determined.
These changes are motivated by some other work on JcloudsLocation that I
will open a pull request for shortly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sjcorbett/brooklyn-server reachable-socket
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/497.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #497
----
commit 721460b17e811180c2a2bc3466c4580cbde56b78
Author: Sam Corbett <[email protected]>
Date: 2016-12-13T18:23:09Z
JcloudsUtil cannot be instantiated and does not implement
JcloudsLocationConfig
commit a6bf79c21b6beb79afdeb1f42aeba2c0865bc497
Author: Sam Corbett <[email protected]>
Date: 2016-12-20T16:55:23Z
Add findOpenSocketsOnNode to ReachableSocketFinder
This changes the semantics of ReachableSocketFinder. Previously it would
return as soon as any host+port was reached. Now it determines the
status of each socket in order. The checks are concurrent but, for
example, if the third of five sockets is reachable the status of the
first and second will also be determined.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
