-
Notifications
You must be signed in to change notification settings - Fork 163
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
Sync sub/pub inconsistent and often fails using go-zmq4 vs C #109
Comments
I had problems getting this to work. Messages were never received. I fixed this by introducing delays. But it seems that in the mean time the C example has changed. It now uses a high water mark. I introduced this into the example, added an explicit termination of the context, and dropped all the delays. Now it works fine on my machine. Tested also in zmq2 and zmq3. Can you please test the updated version? |
Will do, I had already tested the HWM but it made no difference, I'll try the context termination and let you know. |
@pebbe I can confirm that adding the context termination as well as the HWM does indeed solve the issue with my setup. I removed all delays and all messages are received consistently now. Removing either of the HWM config or the deferred Term of the context breaks it again. Without HWM of 1.1M & with deferred context term:
with HWM of 1.1M & deferred context term:
|
Running the following example from the guide; "Node Coordination"
http://zguide.zeromq.org/page:all#Node-Coordination
but using the modified examples from this repository;
https://github.com/pebbe/zmq4/blob/master/examples/syncpub.go
and
https://github.com/pebbe/zmq4/blob/master/examples/syncsub.go
fail almost every time. Running the original guide examples in C succeed every time with the same conditions.
I am using TCP, client and server are on the same machine, compiling against go1.8.3 linux/amd64. Using libzmq5 (4.1.4-7 amd64) on Ubuntu 16.04 amd64 and kernel 4.8.0-58.
Playing around with timings changes the behaviour but is not acceptable for a usable system.
The text was updated successfully, but these errors were encountered: