There were 6 binding +1 votes and no other votes. The vote has passed.
I will add the files to the dist release repo and create the final tag
shortly. The website will be updated after the release has had time to
sync to the mirrors.
Thanks to everybody for testing/voting.
--
The Apache Qpid community is pleased to announce the immediate availability
of Apache Qpid C++ 1.39.0.
Apache Qpid (https://qpid.apache.org) is a cross-platform messaging solution
that implements the Advanced Message Queuing Protocol (AMQP,
https://www.amqp.org). It provides message brokers writte
On 29/10/18 21:45, rammohan ganapavarapu wrote:
I will try to produce, do have any suggestions on what to check in trace
logs?
for qpidd, adding --log-enable trace+:Network to whatever other logging
options you have should do it
---
I will try to produce, do have any suggestions on what to check in trace
logs?
On Fri, Oct 26, 2018 at 2:15 AM Gordon Sim wrote:
> On 26/10/18 00:44, rammohan ganapavarapu wrote:
> > Any idea when do we see this error?
>
> In AMQP 0-10, the connection-close frame allows an informational message
On 29/10/18 20:41, rammohan ganapavarapu wrote:
Now i understand your earlier statement "
*Messages that are larger than a single page are not supported at present*"
since paging uses OS page size (4096) and default page factor is 1, if my
message is bigger than this it will throw error message "
Gordon,
Yes, i am using AMQP 1.0 client. I am ok if journals grow as i have enough
disk space, but one question is once the queue depth is cleared (messages
got consumed), disk space will retain right?
Now i understand your earlier statement "
*Messages that are larger than a single page are not
On 29/10/18 18:21, rammohan ganapavarapu wrote:
On Mon, Oct 29, 2018 at 10:00 AM Gordon Sim wrote:
On 28/10/18 02:23, rammohan ganapavarapu wrote:
Hi,
I have create a durable queue with following arguments:
qpid.paging=True
durable=true
qpid.max_pages_loaded=10
qpid.page_factor=1
so this me
Thank you Gordon, I please check my inline comments.
Ram
On Mon, Oct 29, 2018 at 10:00 AM Gordon Sim wrote:
> On 28/10/18 02:23, rammohan ganapavarapu wrote:
> > Hi,
> >
> > I have create a durable queue with following arguments:
> > qpid.paging=True
> > durable=true
> > qpid.max_pages_loaded=
On 28/10/18 02:23, rammohan ganapavarapu wrote:
Hi,
I have create a durable queue with following arguments:
qpid.paging=True
durable=true
qpid.max_pages_loaded=10
qpid.page_factor=1
so this means my broker will keep 10 * 4028 = 4kb worth of messages (un
consumed) in the memory and offload the i
Any help?
Thanks,
Ram
On Sat, Oct 27, 2018 at 7:23 PM rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:
> Hi,
>
> I have create a durable queue with following arguments:
> qpid.paging=True
> durable=true
> qpid.max_pages_loaded=10
> qpid.page_factor=1
>
> so this means my broker will keep
Yes you can go ahead.
Thanks a lot for the fix.
Olivier
-Original Message-
From: Rob Godfrey
Sent: lundi 29 octobre 2018 16:16
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
Hi Olivier,
I'm not terribly surprised... I've not tested extensively with JDB
Hi Olivier,
I'm not terribly surprised... I've not tested extensively with JDBC, but my
experience with BDB and batch sizes was similar. If you are happy with the
original patch I'll apply that on trunk from QPID-8242.
-- Rob
On Mon, 29 Oct 2018 at 15:41, VERMEULEN Olivier
wrote:
> Hello Rob,
Hello Rob,
I modified your patch to set a minimum batch size of 10 but didn't see any
improvement in the overall throughput...
Olivier
-Original Message-
From: Rob Godfrey
Sent: mardi 2 octobre 2018 18:08
To: users@qpid.apache.org
Subject: Re: [Broker-J] JDBC message store performance
aconway.rh wrote
> Can you try your case with the latest source on the master branch? This
> may
> be a symptom of a recently fixed bug:
>
> PROTON-1953: [go] occasional client/server hang with high volume of
> messages
>
> Although the bug was observed with many small messages, I think it could
14 matches
Mail list logo
