Re: Receing re-delivered messages using Qpid JMS 0.11.1 with Azure Service Bus AMQP Connectivity

Hi Rob, We followed your suggestion by setting jms.prefetchPolicy.all=1 and this solution help us to resolve the message re-delivery and out of memory issue for AMQP Connectivity . We are running this connectivity now from all most more than a month and see that , it is smooth and stable

Re: [Dispatch Router] List of connected producers

Thank you both, I will try what you suggested. I was wondering why the phases are actually named "0" and "1" as this a bit confusing. Wouldn't a more meaningful string representation be better especially for the users? Adel From: Gordon Sim

Re: [Dispatch Router] List of connected producers

On 05/07/17 20:01, Ted Ross wrote: You can query a list of links (org.apache.qpid.dispatch.router.link) with attribute "owningAddr" equal to the addresses of the waypoint (phase 0 for producers, phase 1 for consumers). I believe that the auto-links will also be included in this list, but can be

Re: [Dispatch Router] List of connected producers

Adel, You can query a list of links (org.apache.qpid.dispatch.router.link) with attribute "owningAddr" equal to the addresses of the waypoint (phase 0 for producers, phase 1 for consumers). I believe that the auto-links will also be included in this list, but can be identified by the reversal of

[Dispatch Router] List of connected producers

Hello, I was wondering if there was a way to get the list of producers (or clients in general) connected to a queue on the dispatch router? Context: We would like to block the deletion of a waypoint as long as someone might be using it. Regards, Adel Get Outlook for

Re: Question about settled flag on a multi-frame transfer

Thanks Rob, I entered a JIRA for this - https://issues.apache.org/jira/browse/PROTON-1514 On Wed, Jul 5, 2017 at 9:30 AM, Rob Godfrey wrote: > I agree the spec is horribly unclear on this point. > > I wish we had said something along the lines of two transfers in a >

Re: Question about settled flag on a multi-frame transfer

I agree the spec is horribly unclear on this point. I wish we had said something along the lines of two transfers in a multi-transfer delivery must either both have the same value for settled, or one must be unset (i.e. you can't have frames for the same transfer saying both settled and not

Question about settled flag on a multi-frame transfer

I have a situation where a receiver (proton python's simple_recv.py) is receiving a multi-frame transfer from a Dispatch Router. The settled flag is false on all the transfer frames except on the last frame which has settled=true as seen here - https://pastebin.com/37SYrg92 Proton considers the