Re: [VOTE] Release Apache Qpid JMS 0.59.0

2021-05-19 Thread Timothy Bish
On 5/19/21 12:44 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.59.0 Qpid JMS client release, 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/jms/0.59.0-rc1/ The maven artifa

Re: [VOTE] Release Apache Qpid JMS 0.59.0

2021-05-19 Thread Robbie Gemmell
Oops. Seems I was too busy checking on my 1.0.0 testing and didn't complete the svn commit as I thought I had. Its there now. On Wed, 19 May 2021 at 19:11, Timothy Bish wrote: > > On 5/19/21 12:44 PM, Robbie Gemmell wrote: > > Hi folks, > > > > I have put together a spin for a 0.59.0 Qpid JMS cli

Re: [VOTE] Release Apache Qpid JMS 1.0.0

2021-05-19 Thread Timothy Bish
On 5/19/21 11:41 AM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 1.0.0 Qpid JMS client release, 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/jms/1.0.0-rc1/ The maven artifact

Re: [VOTE] Release Apache Qpid JMS 0.59.0

2021-05-19 Thread Timothy Bish
On 5/19/21 12:44 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.59.0 Qpid JMS client release, 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/jms/0.59.0-rc1/ This path is in

Re: [VOTE] Release Apache Qpid JMS 1.0.0

2021-05-19 Thread Robbie Gemmell
On Wed, 19 May 2021 at 16:41, Robbie Gemmell wrote: > > Hi folks, > > I have put together a spin for a 1.0.0 Qpid JMS client release, > 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/jms/1.0.0-rc

[VOTE] Release Apache Qpid JMS 0.59.0

2021-05-19 Thread Robbie Gemmell
Hi folks, I have put together a spin for a 0.59.0 Qpid JMS client release, 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/jms/0.59.0-rc1/ The maven artifacts are also staged for now at: https://repos

[VOTE] Release Apache Qpid JMS 1.0.0

2021-05-19 Thread Robbie Gemmell
Hi folks, I have put together a spin for a 1.0.0 Qpid JMS client release, 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/jms/1.0.0-rc1/ The maven artifacts are also staged for now at: https://reposit

Re: Message Persistence in Qpid Broker C++ (1.39)

2021-05-19 Thread Rob Godfrey
On Wed, 19 May 2021 at 17:04, Gordon Sim wrote: > On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy wrote: > > Is Broker - J optimized for the below mentioned scenario. > > I believe the java broker will indeed perform better for synchronous > publish. Best thing is to run a quick test though. > B

Re: Message Persistence in Qpid Broker C++ (1.39)

2021-05-19 Thread Gordon Sim
On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy wrote: > Is Broker - J optimized for the below mentioned scenario. I believe the java broker will indeed perform better for synchronous publish. Best thing is to run a quick test though. -

RE: Message Persistence in Qpid Broker C++ (1.39)

2021-05-19 Thread Namitha, Nancy
Hi Gordon, Thanks for the info, that helps a lot. Is Broker - J optimized for the below mentioned scenario. Regards, Nancy -Original Message- From: Gordon Sim [mailto:g...@redhat.com] Sent: Wednesday, May 19, 2021 2:10 PM To: users@qpid.apache.org Subject: Re: Message Persistenc

Re: Message Persistence in Qpid Broker C++ (1.39)

2021-05-19 Thread Gordon Sim
On Wed, May 19, 2021 at 5:09 AM Namitha, Nancy wrote: >I have deployed Qpid Broker C++ v 1.39 package on Ubuntu 18.4. > And have enabled persistence using linearstore libraries. And I am using > AMQP 1.0 Client Library for GO (https://github.com/Azure/go-amqp) for > sending a

Re: Message Persistence in Qpid Broker C++ (1.39)

2021-05-19 Thread Robbie Gemmell
The C++ broker operates a journal flush on a timer, which defaults to 0.5 seconds. For AMQP 1.0 usage this timer is the only event that makes the broker flush the durable messages to disk, and it doesnt acknowledge a durable message until it has, so for synchronous sends (as it sounds like you are