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.

Sign up for GitHub

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

Jump to bottom

tcp sometimes fails to get a port #48

Closed
gdamore opened this issue Aug 9, 2017 · 0 comments
Closed

tcp sometimes fails to get a port #48

gdamore opened this issue Aug 9, 2017 · 0 comments
Labels
bug

Comments

@gdamore
Copy link
Contributor

gdamore commented Aug 9, 2017

We see occasional errors from the TCP test at travis where it seems to fail to obtain a port, and hence listen() fails.

Probably we need to avoid hitting the same port over and over again -- my theory is that we are hitting port reuse and the mandatory TCP TIME_FIN delay.
@gdamore gdamore added the bug label Aug 9, 2017
muryliang pushed a commit to muryliang/nng that referenced this issue Mar 30, 2023
@gdamore
fixes nanomsg#48 Figure out appveyor again
47be3a9 
Hopefully this works.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gdamore