So the scenario is this I think The SUB subscribes to say "order" The pub does a pair of sends as shown. p.send (topic, ZMQ.SNDMORE); p.send (data, 0); The SUB which is doing a pair of recv(0)s, one for the "order" in the topic header of the two part message and a second for the data, entirely misses the first message sent.
Now if the subscription is for 'everything" Ie.an empty byte, the behavior is a bit different. The header (first part) is "lost" and then all subsequent "parts" are received. This throws things off thereafter of course by the amount of the one "missed" part. As opposed to the entire first message when there is an actual subscription filter string. tx From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Foster Sent: Wednesday, March 21, 2012 9:29 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] PUB SUB in zmq 2.1.11 I suspect this is caused by the time required to try reconnecting (it gets progressively longer). Don't put a sleep between the connect and bind, just before the sending first message. Joshua On Mar 21, 2012, at 6:56 AM, Doherty, Kevin wrote: Folks, I'm new to the mail list. Has there been any report of an issue with zmq 2.1.11 where the first message is lost in a pub-sub arrangement *but* Not because of the slow subscriber. Ie. when I send my first message it seems to not get delivered Despite a *very* long delay between the following steps. connect in the sub - bind in the pub - send first message from the pub Same issue if I Bind in pub - connect in sub - send first message from pub With long delays between all of the above ? Tx++ ________________________________ The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ________________________________ _______________________________________________ zeromq-dev mailing list [email protected]<mailto:[email protected]> http://lists.zeromq.org/mailman/listinfo/zeromq-dev ###################################################################### The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ######################################################################
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
