[zeromq-dev] zeromq-dev Digest, Vol 44, Issue 1

[Eric Pederson]

I'll double check but in our case the socket is only used in a
single thread which loops, polls and recvs.

-- Eric

>
> Date: Fri, 1 Nov 2019 20:22:36 +0200
> From: Doron Somech <somdoron at gmail.com>
> To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
> Subject: Re: [zeromq-dev] Assertion failed: !_more fq.cpp:112
>
> It is usually happens when you are using the socket from multiple threads.
>
> That includes recv, send or polling.
>
>
> On Fri, Nov 1, 2019, 20:13 Eric Pederson <ericacm at gmail.com> wrote:
>
> > Hello -
> >
> >
> > We are intermittently running into an issue related to:
> > https://github.com/zeromq/libzmq/issues/2163
> >
> >
> > In that issue they diagnose the problem as trying read additional parts
> of
> > a message from a SUB socket that has been disconnected.
> >
> >
> > In our code we log whenever we disconnect and we are not getting any log
> > messages.  In addition, the logic is single threaded and it's impossible
> to
> > disconnect while a read is taking place.
> >
> >
> > Is it possible for the remote (PUB) side to disconnect while we are in
> the
> > middle of reading to cause this problem?
> >
> >
> > We are running libzmq 4.3.2 on Linux, gcc 5.3.2.
> >
> >
> > The assertion and stack trace are below.
> >
> >
> > Thanks,
> >
> >
> > INF 10/31 12:36:49.544022950 Assertion failed: !_more
> > (/libzmq/src/fq.cpp:112)
> >
> >
> >
> > Thread 1 (Thread 0x7faf226f1700 (LWP 169912)):
> >
> > #0  0x00000037de432495 in raise () from /lib64/libc.so.6
> >
> > #1  0x00000037de433c75 in abort () from /lib64/libc.so.6
> >
> > #2  0x00000000009571ae in zmq::zmq_abort(char const*) ()
> >
> > #3  0x0000000000997a08 in zmq::fq_t::recvpipe(zmq::msg_t*, zmq::pipe_t**)
> > ()
> >
> > #4  0x000000000097a1a3 in zmq::xsub_t::xrecv(zmq::msg_t*) ()
> >
> > #5  0x00000000009674f0 in zmq::socket_base_t::recv(zmq::msg_t*, int) ()
> >
> > #6  0x0000000000943320 in zmq_msg_recv ()
> >
> > #7  0x0000000000901691 in zmq::socket_t::recv (flags_=0, this=0x2235540,
> > msg_=0x7faf226f0be0) at zmq.hpp:724
> >
> > #8  ZMQMessageTransport::deliverEvent (this=0x19c3f40,
> topic="ClassicUser",
> >  socket=...) at ZMQMessageTransport.cpp:123
> >
> > #9  0x000000000090d9e8 in ZmqGroups::event (this=this at entry=0x19c6a00)
> at
> > ZmqGroups.cpp:159
> >
> > #10 0x000000000090dbbb in ZmqGroups::loop (this=0x19c6a00) at
> > ZmqGroups.cpp:74
> >
> > #11 0x000000000092a524 in ZmqLoop::runTheLoop (self=0x19c6a00) at
> > ZmqLoop.cpp:123
> >
> > #12 0x0000000000f521b0 in execute_native_thread_routine ()
> >
> > #13 0x00000037de807aa1 in start_thread () from /lib64/libpthread.so.0
> >
> > #14 0x00000037de4e8bcd in clone () from /lib64/libc.so.6
> >
> > Any ideas would be appreciated.
> >
> > Thanks!
> >
> >
> > -- Eric
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org
> > https://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20191101/e620f024/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
> ------------------------------
>
> End of zeromq-dev Digest, Vol 44, Issue 1
> *****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20191102/f0bcdf0d/attachment.htm>