-
Notifications
You must be signed in to change notification settings - Fork 484
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
ZMonitor stuck on close #984
Comments
I confirm the same behavior with 0.6.0. |
Commenting out Exception in thread "reaper-1" java.lang.AssertionError
at zmq.Own.unregisterTermAck(Own.java:228)
at zmq.SocketBase.pipeTerminated(SocketBase.java:1403)
at zmq.pipe.Pipe.processPipeTermAck(Pipe.java:413)
at zmq.ZObject.processCommand(ZObject.java:91)
at zmq.Command.process(Command.java:79)
at zmq.SocketBase.processCommands(SocketBase.java:1178)
at zmq.SocketBase.inEvent(SocketBase.java:1336)
at zmq.poll.Poller.run(Poller.java:275) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a setup like the following (in version 0.5.4):
From time to time,
monitor.close()
gets stuck, using 100% of a CPU, whilecontext.close()
never gets to run. (Meantime, the monitoring thread manages to effectively terminate.)The text was updated successfully, but these errors were encountered: