On Tue, Oct 29, 2019 at 6:23 PM VERMEULEN Olivier < [email protected]> wrote:
> Hello, > > Yes the waypoint address (in from broker) is using a multicast > distribution. > Unfortunately skipping the broker is not an option for us right now. > Our whole architecture relies on the broker to guarantee that no messages > will ever be lost... > For information we're asking for a quick workaround because we're facing > this problem on a client production environment... > Are you looking for a patch you can apply locally to work around your issue? > > Thanks, > Olivier > > -----Original Message----- > From: Ken Giusti <[email protected]> > Sent: mardi 29 octobre 2019 18:07 > To: users <[email protected]> > Subject: Re: multicast without consumers > > On Tue, Oct 29, 2019 at 11:54 AM jeremy <[email protected]> wrote: > > > Hello Gordon, > > > > We debugged the dispatch router, and fell on the code which releases > > undeliverable messages( > > https://github.com/apache/qpid-dispatch/blob/1.5.0/src/router_core/tra > > nsfer.c#L869 > > ). > > > > Check the comment on line 879. It states that if the distribution is > > multicast, the credit will be replenished after the release. The issue > > that introduced this behavior is: > > https://issues.apache.org/jira/browse/DISPATCH-1012 > > > > > Is the waypoint address (in from broker) using multicast distribution? > > The router treats multicast addresses like topics - you can publish to a > multicast address (topic) regardless of the presence of consumers. That's > the reason credit is being replenished even when no consumers are present. > > That's probably what's happening here - broker sends first queued message > to the router, which attempts to send it to the topic. Since there are no > consumers (and the message is sent from the broker as unsettled) the > router cannot deliver it so it returns the released status. The released > status causes the broker to redeliver the message. Repeat. > > > > > > In fact, we need an urgent fix/workaround for this. Perhaps there is a > > quick workaround, awaiting the full analysis of this problem? > > > > > As a work around can you avoid sending these multicast messages to the > broker queue? In other words send them directly to the router instead of > using a waypoint? > > > > > Thanks > > > > > > > > > > ----- > > Cheers, > > Jeremy > > -- > > Sent from: > > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > > > -- > -K > ******************************* > 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. >
