Is the handover option enabled?
On Fri, Sep 16, 2016 at 11:13 AM, Ranjeet Kumar <xs2ranj...@gmail.com> wrote: > Hi Martin, > > Yes, it is very often. I am having 100k clients connecting with my server. > So in order to run the application i had commented the line from fq.cpp 117 > zmq_assert (!more); > > And now it is working for me. > > > Thanks > (Ranjeet Kumar) > > > On Fri, Sep 16, 2016 at 12:18 AM, Martin Hurton <hurt...@gmail.com> wrote: >> >> Hi Ranjeet, >> >> Is this easy to reproduce? Thanks. >> >> - Martin >> >> On Sat, Sep 10, 2016 at 3:17 PM, Ranjeet Kumar <xs2ranj...@gmail.com> >> wrote: >>> >>> Hi, >>> >>> I am using zeromq 4.1.5 and czmq 3.0.2. I am using the server-client as >>> router dealer. I am getting this Assertion failed: !more (src/fq.cpp:117) >>> issue while 50k clients starts making connecting with the server. >>> >>> stack trace is below: >>> Assertion failed: !more (src/fq.cpp:117) >>> >>> Program received signal SIGABRT, Aborted. >>> [Switching to Thread 0x7ffff490d700 (LWP 24885)] >>> 0x00007ffff68f15f7 in raise () from /lib64/libc.so.6 >>> Missing separate debuginfos, use: debuginfo-install >>> glibc-2.17-106.el7_2.6.x86_64 libgcc-4.8.5-4.el7.x86_64 >>> libstdc++-4.8.5-4.el7.x86_64 >>> (gdb) bt >>> #0 0x00007ffff68f15f7 in raise () from /lib64/libc.so.6 >>> #1 0x00007ffff68f2ce8 in abort () from /lib64/libc.so.6 >>> #2 0x00007ffff7b8f769 in zmq::zmq_abort >>> (errmsg_=errmsg_@entry=0x7ffff7bc1eca "!more") at src/err.cpp:83 >>> #3 0x00007ffff7b8fccd in zmq::fq_t::recvpipe (this=this@entry=0x60bdc0, >>> msg_=msg_@entry=0x7ffff490ce60, pipe_=pipe_@entry=0x7ffff490cd08) at >>> src/fq.cpp:117 >>> #4 0x00007ffff7ba3423 in zmq::router_t::xrecv (this=0x60b8d0, >>> msg_=0x7ffff490ce60) at src/router.cpp:301 >>> #5 0x00007ffff7ba878b in zmq::socket_base_t::recv >>> (this=this@entry=0x60b8d0, msg_=msg_@entry=0x7ffff490ce60, >>> flags_=flags_@entry=0) at src/socket_base.cpp:910 >>> #6 0x00007ffff7ba1015 in forward (from_=from_@entry=0x60b8d0, >>> to_=to_@entry=0x60c0b0, capture_=capture_@entry=0x0, msg_=...) at >>> src/proxy.cpp:81 >>> #7 0x00007ffff7ba11e7 in zmq::proxy (frontend_=0x60b8d0, >>> backend_=0x60c0b0, capture_=0x0, control_=0x0) at src/proxy.cpp:188 >>> #8 0x0000000000403fcf in broker_task (args=0x0) at push_server.cpp:1348 >>> #9 0x00007ffff791978f in s_thread_shim (args=0x60d590) at >>> src/zthread.c:84 >>> #10 0x00007ffff76b6dc5 in start_thread () from /lib64/libpthread.so.0 >>> #11 0x00007ffff69b2ced in clone () from /lib64/libc.so.6 >>> >>> Any suggestion to fix this issue. >>> >>> Thanks >>> (Ranjeet Kumar) >>> >>> >>> >>> _______________________________________________ >>> zeromq-dev mailing list >>> zeromq-dev@lists.zeromq.org >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> >> >> _______________________________________________ >> zeromq-dev mailing list >> zeromq-dev@lists.zeromq.org >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
