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.

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

Reopen issue #840 #950

Open
zcteo opened this issue Nov 3, 2020 · 3 comments
Open

Reopen issue #840 #950

zcteo opened this issue Nov 3, 2020 · 3 comments

Comments

@zcteo
Copy link

zcteo commented Nov 3, 2020

issue#840
@dxdjgl
sometimes, e.Socket could throw an exception

screen

Originally posted by @zcteo in #840 (comment)

@zcteo
Copy link
Author

zcteo commented Nov 3, 2020

current netmq version: 4.0.1.0

@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because it has not had activity for 365 days. It will be closed if no further activity occurs within 56 days. Thank you for your contributions.

@stale stale bot added the stale label Apr 17, 2022
@hryhorasz
Copy link

This is still an issue. There is no way to get the RemoteEndPoint of the disconnected socket because it's null.

@stale stale bot removed the stale label Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants