[zeromq-dev] zmq_socket_monitor blocks port of REP/REQ TCP/IP in C

Goswin von Brederlow goswin-v-b at web.de
Tue Jan 21 12:24:05 CET 2014

On Tue, Jan 21, 2014 at 08:15:58AM +0000, Björn Kuhlbrodt wrote:
> Hi Peter
> Hmm, too bad. As I said, socket_monitor is working fine (although
> not perfect maybe) in our application. It just does not close without
> messing up the context.

In what way does it mess up the context? Please open an issue in the
bug tracker.

> And if it's not good for watching the connection and messes up the
> context, how about a little warning in the doc: devolopers tool,
> instable, beta, ....? It took us _some_ time to isolate socket_monitor
> as the culprit.
> Best regards
> Björn

He didn't say it was no good. He said that not all problems will cause
a disconnect to show up on the monitor socket. Simplest example: The
peer goes into an endless loop and doesn't respond/send messages
anymore. The socket will be kept alive by the kernel so you won't get
a disconnect. A heartbeat though will tell you that the peer is


More information about the zeromq-dev mailing list