Hello Chuck,
I'm very interested!
Will give it a try next week.
Thanks,
Olivier
-----Original Message-----
From: Chuck Rolke <cro...@redhat.com>
Sent: mercredi 17 avril 2019 22:51
To: users@qpid.apache.org
Subject: Re: [Dispatch-router] Multicast
Hi Olivier,
I've developed tooling to help find problems like the one you describe.
Could you give it a try?
To use it:
1. Turn on trace logging. For the most part just SERVER trace+ will do it but
DEFAULT trace+ gets the most detail. Save each router's log to a separate file.
Add something like this to your router config files:
log {
outputFile: <router-name>.log
enable: trace+
module: DEFAULT
}
2. Delete existing log files for a clean analysis.
3. Run your test so it fails due to the race condition.
4. Stop the routers
5. Change cwd to the directory with the log files.
6. Scrape the logs and generate and html file with AMQP analysis:
qpid-dispatch/tools/scraper/scraper.py -f *.log > test.html 7. Open the
test.html file with a browser:
firefox test.html
8. In the Log Data section you will find the router and client traffic.
I suspect that the client connect sequence and data patterns will be visible.
-Chuck
----- Original Message -----
> From: "VERMEULEN Olivier" <olivier.vermeu...@murex.com>
> To: users@qpid.apache.org
> Sent: Wednesday, April 17, 2019 10:10:49 AM
> Subject: RE: [Dispatch-router] Multicast
>
> Hello Gordon,
>
> Thanks for your help.
> After struggling for a few hours I also managed to make my use case work.
> Actually the test I was using was too fast, leading to 2 problems.
> First, the 2 dispatch-routers didn't have time to establish the
> inter-router route.
> Second, randomly the consumers were not yet registered in the
> dispatch-routers when the message was sent.
>
> Olivier
>
> -----Original Message-----
> From: Gordon Sim <g...@redhat.com>
> Sent: mercredi 17 avril 2019 12:39
> To: users@qpid.apache.org
> Subject: Re: [Dispatch-router] Multicast
>
> On 17/04/2019 8:50 am, VERMEULEN Olivier wrote:
> > I have a question regarding the use of multicast with the dispatch-router.
> > I have 2 dispatch-routers and 1 broker with a topic/queue configuration.
> > All my addresses are configured as waypoints and the ones for the
> > queue are also configured as multicast.
> > When I put 2 listeners on the queue, 1 connected to each
> > dispatch-router, only one of them is receiving the message...
> > Is this supposed to be a supported use case? Am I missing something
> > in the configuration?
>
> I tried this out with the attached config files and a broker on 7777
> and it worked as expected. Two receivers, one on each router, both saw
> all the sent messages.
>
> In this case there is only one broker and it is connected to by only
> one of the routers. I did try with each router connecting to the
> broker also, and that works as well. However, as expected, since the
> address is multicast in both phases, the messages are duplicated (each
> message is sent down both links to the broker).
> *******************************
> 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 authorized 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: users-unsubscr...@qpid.apache.org For
> additional commands, e-mail: users-h...@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
commands, e-mail: users-h...@qpid.apache.org
*******************************
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 authorized 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.
