#369 has been fixed, but the same issue apparently affects REQ/REP sockets, which still suffer from the issue, which is opened as #370.
On Mon, May 28, 2012 at 1:07 AM, Pieter Hintjens <[email protected]> wrote: > I've confirmed the issue with a C test case: > https://github.com/zeromq/issues/tree/master/369 > > On Sun, May 27, 2012 at 8:49 PM, MinRK <[email protected]> wrote: > > The ROUTER/DEALER pattern doesn't work after the ROUTER restarts unless > you > > restart the DEALER as well. > > > > > > Summary: > > > > 1. ROUTER binds, DEALER connects > > 2. ROUTER process restarts (or close & bind new ROUTER) > > 3. routing, prefixes, and messages are broken hereafter > > > > Symptoms: first send on a DEALER after the new ROUTER comes up will end > up > > setting the IDENTITY, rather than making a receivable message. Only after > > the second such message is sent by the DEALER does the ROUTER actually > have > > a message to receive. > > > > Opened as LIBZMQ-369 with attached python test case, which I hope is > > considered a blocker for a libzmq-3 stable release. > > > > -MinRK > > > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
