development list
Subject: Re: [zeromq-dev] [pyzmq] Cython vs CFFI backends
I just went through a similar experience. In my case, the problem was that
close()
wasn't called from the same thread that created the socket.
You may find the explanations here useful:
http://zeromq.org/whitepapers:0mq
Hey all.
I am debugging a hang in my application: the ctx.linger option is set
before creating any sockets, but it still hangs on ctx.term().
While scanning the pyzmq code I noticed the CFFI backend supports passing a
linger parameter to the term() call whereas the Cython backend does not.
This
I just went through a similar experience. In my case, the problem was that
close()
wasn't called from the same thread that created the socket.
You may find the explanations here useful:
http://zeromq.org/whitepapers:0mq-termination
Debugging these hands is a real pain. Is there anything that
I had a similar issue with the ruby gem “rbczmq” which wraps CZMQ.
CZMQ itself wraps the ZMQ context and does its own socket close (with linger
set) before asking ZMQ context terminate. This process is not thread safe and I
needed to use a mutex to ensure that no other sockets were closed
On Sun, Apr 13, 2014 at 3:29 PM, Alexander S. alexan...@thequery.netwrote:
Hey all.
I am debugging a hang in my application: the ctx.linger option is set
before creating any sockets, but it still hangs on ctx.term().
While scanning the pyzmq code I noticed the CFFI backend supports passing
On Sun, Apr 13, 2014 at 7:12 PM, Matt Connolly matt.conno...@me.com wrote:
I had a similar issue with the ruby gem “rbczmq” which wraps CZMQ.
CZMQ itself wraps the ZMQ context and does its own socket close (with
linger set) before asking ZMQ context terminate. This process is not thread
safe
