-
Notifications
You must be signed in to change notification settings - Fork 71
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
socket exception starting kernel (Ubuntu 16.04.1, Mono 4.6.0) #90
Comments
This appears to be a Mono 4.6.* issue with NetMQ. For reference: I installed Mono 4.6.1 and I now have the same issue. |
sylvanc
added a commit
to sylvanc/mono
that referenced
this issue
Oct 31, 2016
SO_REUSEADDR and SO_REUSEPORT are fundamentally different. This exception seems to have been put in place to address the lack of the latter on older Linux kernels for TCP. However, the change in fact raises an exception when SO_REUSEADDR is used, which causes failures in server applications, which may use SO_REUSEADDR to avoid WAIT state timeouts. Description of SO_REUSEADDR and SO_REUSEPORT differences: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Some problems caused by raising this exception: zeromq/netmq#623 zeromq/netmq#592 fsprojects/IfSharp#90
luhenry
pushed a commit
to mono/mono
that referenced
this issue
Nov 1, 2016
SO_REUSEADDR and SO_REUSEPORT are fundamentally different. This exception seems to have been put in place to address the lack of the latter on older Linux kernels for TCP. However, the change in fact raises an exception when SO_REUSEADDR is used, which causes failures in server applications, which may use SO_REUSEADDR to avoid WAIT state timeouts. Description of SO_REUSEADDR and SO_REUSEPORT differences: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Some problems caused by raising this exception: zeromq/netmq#623 zeromq/netmq#592 fsprojects/IfSharp#90
luhenry
pushed a commit
to luhenry/mono
that referenced
this issue
Nov 2, 2016
SO_REUSEADDR and SO_REUSEPORT are fundamentally different. This exception seems to have been put in place to address the lack of the latter on older Linux kernels for TCP. However, the change in fact raises an exception when SO_REUSEADDR is used, which causes failures in server applications, which may use SO_REUSEADDR to avoid WAIT state timeouts. Description of SO_REUSEADDR and SO_REUSEPORT differences: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Some problems caused by raising this exception: zeromq/netmq#623 zeromq/netmq#592 fsprojects/IfSharp#90
luhenry
added a commit
to mono/mono
that referenced
this issue
Nov 3, 2016
SO_REUSEADDR and SO_REUSEPORT are fundamentally different. This exception seems to have been put in place to address the lack of the latter on older Linux kernels for TCP. However, the change in fact raises an exception when SO_REUSEADDR is used, which causes failures in server applications, which may use SO_REUSEADDR to avoid WAIT state timeouts. Description of SO_REUSEADDR and SO_REUSEPORT differences: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Some problems caused by raising this exception: zeromq/netmq#623 zeromq/netmq#592 fsprojects/IfSharp#90
I've submitted a Mono patch that will ship with Mono 4.8. Meanwhile, Mono 4.4 does work, but Mono 4.6 does not. I'm closing this issue here since it's a Mono bug. Thanks very much for the report! |
luhenry
pushed a commit
to luhenry/mono
that referenced
this issue
Dec 6, 2016
SO_REUSEADDR and SO_REUSEPORT are fundamentally different. This exception seems to have been put in place to address the lack of the latter on older Linux kernels for TCP. However, the change in fact raises an exception when SO_REUSEADDR is used, which causes failures in server applications, which may use SO_REUSEADDR to avoid WAIT state timeouts. Description of SO_REUSEADDR and SO_REUSEPORT differences: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Some problems caused by raising this exception: zeromq/netmq#623 zeromq/netmq#592 fsprojects/IfSharp#90
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: