Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)

+1 * Built from source with Proton at d28fecf, three commits after 0.23.0. * Ran self tests - Original Message - > From: "Ganesh Murthy" > To: users@qpid.apache.org > Sent: Friday, May 25, 2018 5:45:30 PM > Subject: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4) > > Hello All, > >

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)

+1 ... I build it from source on CentOS7 and used with different AMQP 1.0 clients. On Fri, May 25, 2018 at 11:45 PM Ganesh Murthy wrote: > Hello All, > > Please cast your vote on this thread to release RC4 as the > official Qpid Dispatch Router version 1.1.0. > > RC4 of Qpid Dispatch

Re: Handling of undeliverable messages in Dispatch Router

On Thu, May 24, 2018 at 1:59 PM, Ganesh Murthy wrote: > On Thu, May 24, 2018 at 1:48 PM, Chuck Rolke wrote: > > > Releasing the messages sounds like the better choice. > > > > It also would be nice if the router could revoke the sender's credit so > > that

[VOTE] Release Apache Qpid Broker-J 7.0.4

Hi all, I built a release candidate for a Qpid Broker-J 7.0.4. Please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.4-rc1 The maven artifacts are also staged for now at:

Apache Qpid and Azure Service bus: Is there internal buffer of Qpid driver that can lead to duplicates/unordered messages processing under load?

We use qpid-jms-client version 0.27.0 to work with Azure SB. What the cause of processing messages out of order under load? Currently we have next situation: 1) read message from SB by driver with JMSXDeliveryCount=1 2) SB place lock and increase deliveryCounter 3) after 5 minutes lock