You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by neykov <gi...@git.apache.org> on 2017/02/16 17:22:48 UTC
[GitHub] brooklyn-server pull request #563: [WIP] Don't SO_REUSEADDR when probing for...
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/563
[WIP] Don't SO_REUSEADDR when probing for available ports
Do not merge, the changes here are meant to test the behaviour on Apache's jenkins slaves.
The changes have the side effect of causing Brooklyn to bump it's default port on each restart if there were existing connections.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/brooklyn-server available-port
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/563.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 #563
----
commit 0be6d4a61e241e2685aac5aad661f23f830cf73e
Author: Svetoslav Neykov <sv...@cloudsoftcorp.com>
Date: 2017-02-16T17:17:33Z
Don't SO_REUSEADDR when probing for available ports
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server issue #563: [WIP] Don't SO_REUSEADDR when probing for availa...
Posted by neykov <gi...@git.apache.org>.
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/563
Using non-`SO_REUSEADDR` sockets seems to work fine on the apache build slaves. On the other hand it prevents us from re-binding to the same port after restarting Brooklyn, so not ideal.
If the problems persist I suggest we add troubleshooting info in the tests. Things like the output of `netstat`, `ip addr show` & similar, which could guide us to the root cause of the failures. See https://github.com/apache/incubator-brooklyn/pull/657 for other ideas.
https://github.com/apache/incubator-brooklyn/pull/662 addresses a similar problem, worth having in mind if someone tries to dig in deeper.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server pull request #563: [WIP] Don't SO_REUSEADDR when probing for...
Posted by neykov <gi...@git.apache.org>.
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/563
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---