[zeromq-dev] ROUTER/DEALER doesn't work after ROUTER restart

MinRK benjaminrk at gmail.com
Mon May 28 20:19:29 CEST 2012


#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 <ph at imatix.com> 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 <benjaminrk at gmail.com> 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
> > zeromq-dev at lists.zeromq.org
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120528/b0db759a/attachment.htm>


More information about the zeromq-dev mailing list