[zeromq-dev] Can we customize a behaviour for in-mem queued messages after reconnect?
artemv zmq
artemv.zmq at gmail.com
Fri Dec 20 14:33:00 CET 2013
hi Pieter,
Here's code: http://pastebin.com/67uRMZKx Threre are two classes, Sender
and Receiver. Start Sender with "-ea" jvm arg and hostname where Receiver
is running. Start Receiver with "-ea" jvm arg.
How to see that messages being redelievered: start Sender, start
Receiver. See in log that Receiver gobbles messages from Sender. Then
stop Receiver process for a 10 seconds, and then start it again. Now,
you should see in Receiver log that messages have been queued for a time as
much as Receiver was down.
2013/12/20 Pieter Hintjens <ph at imatix.com>
> On Fri, Dec 20, 2013 at 11:16 AM, artemv zmq <artemv.zmq at gmail.com> wrote:
>
> > So the question arised -- how to not redeliver messages upon
> reconnect?
>
> If you have a minimal test case that shows a message being redelivered
> on reconnect, can we see it?
>
> -Pieter
> _______________________________________________
> 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/20131220/fe954ef2/attachment.htm>
More information about the zeromq-dev
mailing list