Indeed with link-routes everything is working as expected. This brings another question though. I see in the docs that if I want to use server-side collectors I must use autolinks. But If want to use non-destructive consumers I have to use linkRoutes. And it looks like I will have to handle both use cases (not at the same time so far). So the question is, can I mix autolinks and linkRoutes in the dispatch-router configuration?
Thanks, Olivier -----Original Message----- From: VERMEULEN Olivier Sent: mercredi 4 juillet 2018 09:23 To: [email protected] Subject: RE: [Dispatch Router] non-destructive consumers Thanks for the quick reply. I will try with link-routes then. Olivier -----Original Message----- From: Ted Ross <[email protected]> Sent: mardi 3 juillet 2018 15:48 To: [email protected] Subject: Re: [Dispatch Router] non-destructive consumers On Tue, Jul 3, 2018 at 9:34 AM, VERMEULEN Olivier <[email protected]> wrote: > Hello, > > I've been playing with the non-destructive consumers fro the past few days. > > First I will explain the use case that works. > If I create a queue on a Broker-J (7.0.3) with ensureNonDestructiveConsumers > set to true and I put a message in it, then any consumer I create for this > queue will read this single message, as expected from non-destructive > consumers. > > Now if I add a Dispatch-Router (0.7.0) in front of my broker, then the first > consumer I create will receive the message but the second one will receive > null... > Did I miss some configuration on the Dispatch-Router side? I assume that you used an auto-link to connect to the broker queue. In this case, there is only one consumer on the queue, the router, and it gets a copy of the message to distribute accordingly. If you used a link-route instead, then each remote consumer would have its own subscription on the queue and get its own copy of the message. Let me know if you'd like a more specific answer with regard to the configuration. -Ted > > Thanks, > Olivier > ******************************* > > This e-mail contains information for the intended recipient only. It may > contain proprietary material or confidential information. If you are not the > intended recipient you are not authorised to distribute, copy or use this > e-mail or any attachment to it. Murex cannot guarantee that it is virus free > and accepts no responsibility for any loss or damage arising from its use. If > you have received this e-mail in error please notify immediately the sender > and delete the original email received, any attachments and all copies from > your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ******************************* This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
