-
Notifications
You must be signed in to change notification settings - Fork 145
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
TcpKeepAliveSettings doesn't work on Linux #398
Comments
netstandard1.3 or 2.0? 1.3 is still using very old 4.1.0 System.Net.Sockets package released in 2016. The fix was made in 2018. Have you tried 2.0 with the latest .net core runtime? |
I think I'm using the new version. Here you can have a look at the app I sent to Red Hat to help them reproduce the issue --> https://github.com/HavretGC/TcpKeepAliveSettings |
Maybe we could address this the same way as it was done for SqlClient? --> dotnet/SqlClient#395 |
That requires us to build multiple targets and lose the benefit of targeting just netstandard. This is what I have found.
Branch |
I was able to run my test app with the changes from Possibly we could ask guys from Red Hat, to confirm that the fix is ok. |
@xinchen10 as per Red Hat:
So do we need anything more carry on with that? |
LGTM to be honest. |
I have merged the change to master. |
Can we expect the release any time soon? :) |
Released 2.4.0. |
I am getting the following exception when, I try to use
TcpKeepAliveSettings
with the app deployed on Linux box. I'm not sure but this should be supported dotnet/corefx#29963. Do we need to make some adjustments in AmqpNetLite to make this work properly on Linux?The text was updated successfully, but these errors were encountered: