[zeromq-dev] Assertion failed: !current_out (xrep.cpp:166)

Victor Nakoryakov nail.xx at gmail.com
Fri Jan 28 17:44:08 CET 2011

Hi all,

I've got a trouble while using XREP socket under relatively high load.
Assertion mentioned crashes my daemon after minute or so. All that
time it is used to reply to xreqs and to initiate message pushes with
manually formed envelope (as an identity of an expected receiver) as
well. Messages are from 40 bytes to 20 KBytes.

As far as I understand looking at C++ code, the problem is attempt to
send a new message while previous message send isn't done. If so, how
could it be? Could it be a threading issue? I done my code in such way
so that a new XREP socket is created for every thread, but there is
just one thread and just one socket on receiving (XREQ) side. Could it
be a reason? I guess no, but who knows. I use python bindings if it
matters, they are 2.1.1 and zeromq itself is 2.1.0.

I'm burning. We're replacing damn RabbitMQ with ZeroMQ in few days
before product launch (eek!). Could somebody help with the problem?

Victor Nakoryakov
nail.xx at gmail
Moscow, Russia


More information about the zeromq-dev mailing list