Hello, We tested against the master and it is now working fine.
Thanks, Olivier -----Original Message----- From: Ganesh Murthy <[email protected]> Sent: jeudi 20 septembre 2018 17:59 To: [email protected] Subject: Re: [Dispatch-Router] max message size Here is the sequence of events we gleaned from the log file (btw, it looks like you sent your router config file but we did not get it, it was stripped) The Router has two Java brokers attached to it and autolinks on the same address to those two brokers 1. A message over 10kb is sent and the router forwards it to Broker 1 over the autolink. The message exceeds the max message size set by the broker and so the broker detaches the autolink and closes the session. The autolink from Router to Broker 1 is now destroyed. The only remaining autolink is to Broker2 2. A message smaller than 10kb is sent and the router sends it on the autolink to Broker 2. (all good here) 3. Once again, a message over 10kb is sent, and that is forwarded to Broker 2 and Broker 2 rejects that messages because it is too big and detaches the link and closes the session. Now the autolinks on Broker 2 are destroyed as well. Now, since both autolinks are gone, any further messages sent to that address 'myQueue' have nowhere to go and hence the final send hangs (the router does not issue a flow to the sender because there are no consumers for the message) On the master branch, we added an enhancement - https://issues.apache.org/jira/browse/DISPATCH-1103 - which would retry and re-establish failed autolinks. This new feature will fix your issue. Unfortunately, this new feature will only be available in Qpid Dispatch 1.4.0 which is scheduled to go out mid to late October. Is it possible for you to get Dispatch running with the latest master branch code and see if this problem goes away? Thanks. On Thu, Sep 20, 2018 at 10:22 AM VERMEULEN Olivier < [email protected]> wrote: > Here are the files. > > Thanks, > Olivier > > -----Original Message----- > From: Ganesh Murthy <[email protected]> > Sent: jeudi 20 septembre 2018 15:19 > To: [email protected] > Subject: Re: [Dispatch-Router] max message size > > Can you please enable trace logging on the router and share the log file? > > To enable trace logging add the following to your router configuration > file. > > log { > module: DEFAULT > enable: trace+ > output: qdrouterd.log > } > > Also please share your router config file if possible and which broker > you are using to test. > > > On Thu, Sep 20, 2018 at 8:47 AM VERMEULEN Olivier < > [email protected]> wrote: > > > Hello, > > > > We did a test with 1 dispatch-router and 2 brokers. > > On the brokers we configured a maximum message size of 10KB. > > The use case is the following: > > > > * We send a message above 10 KB: we receive a "failure at remote" > > exception from the dispatch-router > > * We send a message under 10KB: send is successful > > * We send a message above 10 KB again: we receive a "failure at > > remote" exception from the dispatch-router > > * We send a message under 10KB again: the send hangs... > > > > This was reproduced with the latest version of the dispatch-router. > > Do you have any idea what is going on and is it a known issue? > > > > 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. > > > ******************************* > > 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.
