[zeromq-dev] flushing (again)
Andrew Hume
andrew at research.att.com
Sun Apr 3 17:24:17 CEST 2011
i am running 2.1.1.
i have a program which essentially does
// sock has been opened as a ZMQ_PUSH over tcp
msendstr(sock, "exit");
ret = zmq_close(sock);
assert(ret == 0);
exit(0);
if i run this, then i've never seen the message get to teh other end.
if i insert a sleep(1) BEFORE the exit (and AFTER the zmq_close), it always arrives at its dest.
i had thought this bug was fixed in 2.1.
or is this one of those "we did all we could; blame tcp/ip" situations?
is there a fix more elegant than sleep(1)?
------------------
Andrew Hume (best -> Telework) +1 623-551-2845
andrew at research.att.com (Work) +1 973-236-2014
AT&T Labs - Research; member of USENIX and LOPSA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110403/d392e1f4/attachment.htm>
More information about the zeromq-dev
mailing list