-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
ZMQ_XPUB_MANUAL subscriptions not properly cleaned up #2601
Comments
bluca
added a commit
to bluca/libzmq
that referenced
this issue
Jun 22, 2017
Solution: remove the pipe from the real trie when a peer disconnects. Also add a unit test that exercises the behaviour by reconnecting a different socket and sending a message that matches. Fixes zeromq#2601 and introduced by zeromq#2042
Thanks for the report and especially for the unit test. Can reproduce, was introduced by: #2042 I'm testing a fix at the moment, will probably send it tomorrow. |
@mrseanmorris please try again from latest master, should be fixed. |
Hi @bluca Your patch fixed the problem. Thanks for the very fast response! Cheers, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I'm working on implementing a service that uses the ZMQ_XPUB_MANUAL feature, and I've come across a what I think is a bug in how subscriptions are cleaned up. The problem happens when a client doesn't cleanly unsubscribe from topics, and instead either closes the socket without cleaning up, or simply just crashes.
After this happens, the subscriptions seem to get out of sync and subsequent clients that connect and subscribe will receive messages on topics for which they did not subscribe.
Here's a simple reproducer that shows the problem :
The text was updated successfully, but these errors were encountered: