> I use ZMQ 2.X with the JZMQ binding. I am trying to debug a typical “java: > Socket.cpp:561: void* get_socket(JNIEnv*, jobject, int): Assertion `s' > failed.” I am probably sending a message on a closed socket, but it is > difficult to correlate my application logs and the assert error. I would > like to activate the ZMQ traces or something similar. > > Is there any way to activate the logs either from JZMQ using a log4j like > configuration or directly from ZMQ using the same kind of mechanism?
I just checked in a fix that removes the assertion and throws an ENOTSOCK in JZMQ. https://github.com/zeromq/jzmq/commit/766ab8fe3869c99b06643bd33120e04cbdfb8ca1 You can log from your catch block _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
