I made a reproducible case in C++ where if you have two subscribers: one listening to "a" and "b" and another listening to "a" "b" and "c" if you close the socket of the subscriber listening to "a" and "b" the other subscriber loses a "b" message for one sequence. I can't seem to reproduce it where it stops getting "b" messages altogether, though, which is what I see in production.
On Wed, Feb 22, 2012 at 4:13 PM, Calvin de Vries <[email protected]>wrote: > I actually do use high water marks already, I don't use identities on > purpose because I don't want the client to be durable. If the client socket > is closed and reopened, it's bad behavior if messages are replayed (in my > case). > > > On Wed, Feb 22, 2012 at 4:04 PM, Justin Cook <[email protected]> wrote: > >> On Wed, Feb 22, 2012 at 8:47 PM, Calvin de Vries >> <[email protected]> wrote: >> > I'm not using ZMQ_IDENTITY on either the server or the client. >> >> If either of you are able to reproduce this, I would recommend setting >> a high water mark and using identities (durable sockets) to see if >> that alleviates the issue. Just a wild guess... >> _______________________________________________ >> 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
