Re: Qpid broker 6.0.4 performance issues

Hi Rob, Again, thank you so much for answering our questions and providing a patch so quickly :) One more question I have: would it be possible to include test cases involving many queues and listeners (in the order of thousands of queues) for future Qpid releases, as part of standard perf

Re: Unconsumed messages can still prevent GC of consumed messages

of queues that we do not create any regular consumer to for a long time. Thanks again for fixing this so quickly (as usual)! Helen On Sun, Nov 1, 2015 at 4:44 PM, Helen Kwong <helenkw...@gmail.com> wrote: > Thanks a lot for looking into this and fixing it so quickly! Will try the > p

Re: Unconsumed messages can still prevent GC of consumed messages

r that will be out by the end of > this week), > > Cheers, > Rob > > On 4 November 2015 at 21:57, Helen Kwong <helenkw...@gmail.com> wrote: > > > Hi Rob, > > > > The patch fixed the issue in our tests. It looks like we ran into the > > problem bec

Re: Unconsumed messages can still prevent GC of consumed messages

Thanks a lot for looking into this and fixing it so quickly! Will try the patch and let you know. Helen On Sat, Oct 31, 2015 at 4:50 PM, Rob Godfrey wrote: > I've raised a jira https://issues.apache.org/jira/browse/QPID-6820 > covering > the issue with state change

Re: NPEs when creating consumers / queues

Hi Keith, just want to let you know that the 0.32 patch did indeed solve the issue we encountered in our tests before. Thanks very much for your help! On Fri, Jul 10, 2015 at 10:48 AM, Helen Kwong helenkw...@gmail.com wrote: Hi Keith, Thanks a lot for the patch! We will try the 0.32 patch

Re: NPEs when creating consumers / queues

Hi Keith, Thanks a lot for the patch! We will try the 0.32 patch with our tests and let you know how it goes. Helen On Fri, Jul 10, 2015 at 6:43 AM, Keith W keith.w...@gmail.com wrote: On 2 July 2015 at 21:50, Rob Godfrey rob.j.godf...@gmail.com wrote: On 2 July 2015 at 21:29, Helen Kwong

Re: NPEs when creating consumers / queues

() method of the queue has completed). I'm about to go to sleep here, and am in meetings most of tmr, so I may not get a chance to dig deeper until later this week - however we'll look to provide some sort of patch to fix this ASAP though. Apologies, Rob On 1 July 2015 at 00:33, Helen Kwong

NPEs when creating consumers / queues

Hi Qpid experts, I am testing using Java broker 0.32 with client 0.16, and have run into NPEs when I create consumers to queues in an initialization step to force the queues to be created. I'm not able to reproduce this reliably, and it's possible that this is triggered by some race condition,

Qpid Java client deadlocks

Hi Qpid gurus, We are using 0.16 Java broker and client on 0-10, and we are running into deadlock issues on the client that involve AMQSession's _messageDeliveryLock and AMQConnection's _failoverMutex, where different threads acquire them in different orders. This is leading to major production

Re: Single consumer across multiple queues

individual queue as a context variable). When Keith gets done with what he's currently working on we'll try to update you on our work on changing the queue threading model around. Cheers, Rob On 31 October 2014 01:19, Helen Kwong helenkw...@gmail.com wrote: Hi Rob, I got around

Re: Possible for unconsumed messages to prevent GC from reclaiming memory held by prior messages?

Hi Rob, just got your fix in trunk and ran our test again, and confirmed that the bug is fixed. Thank you again for your help and responding so quickly! On Thu, Oct 30, 2014 at 5:03 AM, Rob Godfrey rob.j.godf...@gmail.com wrote: Thank you for those kind words. It's always gratifying to be

Single consumer across multiple queues

Hi Rob, I got around to doing some testing on the multi-queue consumer feature you added. So far things have looked good mostly, but there is one issue I've run into and would like your help on. When we had single-queue consumers, we had fair allocation behavior across queues, in the sense that

Re: Possible for unconsumed messages to prevent GC from reclaiming memory held by prior messages?

Hi Rob, I'll describe what I see from a heap dump during a run of the test Dan described. I'm running the 0.32 broker and client, though I've also looked at a heap dump with the 0.16 broker and client and have seen similar patterns. The steady state heap size of my broker is ~200MB. After running

Re: 1 Queue with 2 Consumers - turn off pre-fetching?

Hi Rob, We have implemented the workaround Dan mentioned before -- by suspending the session with sendSuspendChannel() and releasing prefetched messages with rejectMessagesForConsumerTag() whenever we detect a long-running message -- and so far it is working as expected. Thank you again for all

Re: 1 Queue with 2 Consumers - turn off pre-fetching?

Hi Rob, We're looking into one idea that you suggested, where you said: It may be possible to code a client library side change without changing the broker (basically reduce consumer credit to 0 as soon as one consumer has a message, and release any messages that have been prefetched), but

Re: Limiting the number of concurrent consumers across multiple queues

improvements for queues with 'shared groups'. Robbie On 17 January 2014 21:38, Helen Kwong helenkw...@gmail.com wrote: Hi Gordon, In the tests that we've run, the time it takes to dequeue messages using selectors seems to increase with the depth of the queue. Since the number

Limiting the number of concurrent consumers across multiple queues

Hi Qpid users / experts, I need to limit the number of consumers concurrently processing messages considered to be in the same group, across multiple queues, and was wondering if anyone has ideas about how to do it. We’re using the Java broker and client, and have multiple queues, each with

Re: Java broker - message grouping in C++ compatibility mode

need something different though, as neither of these routes would really help there. Robbie On 11 January 2014 01:03, Helen Kwong helenkw...@gmail.com wrote: Hi Robbie, I did some more testing to see whether message grouping will work for us, and compared the dequeue performance

Re: Java broker - message grouping in C++ compatibility mode

? Thanks, Helen On 13 January 2014 20:34, Helen Kwong helenkw...@gmail.com wrote: Hi Robbie, I am actually still running version 0.16 of the broker. It will take me a little time to set up the trunk code and rebuild and rerun the experiments. Do you think your fix will likely make

Re: Java broker - message grouping in C++ compatibility mode

a group key value in that mode are simply not grouped in any way. On 8 January 2014 04:41, Robbie Gemmell robbie.gemm...@gmail.com wrote: On 8 January 2014 04:33, Helen Kwong helenkw...@gmail.com wrote: Oh I see, I thought what you meant was that I could only alter the default group

Java broker - message grouping in C++ compatibility mode

Hi, I use the Java broker and client, version 0.16, and am considering using the message grouping feature ( http://qpid.apache.org/releases/qpid-0.24/java-broker/book/Java-Broker-Queues.html#Java-Broker-Queues-OtherTypes-Message-Grouping). From testing I've done, there seems to be a bug with the

Re: Java broker - message grouping in C++ compatibility mode

that is possible. https://issues.apache.org/jira/browse/QPID-5450 Robbie On 8 January 2014 02:43, Helen Kwong helenkw...@gmail.com wrote: Hi, I use the Java broker and client, version 0.16, and am considering using the message grouping feature ( http://qpid.apache.org/releases/qpid-0.24

Re: Java broker - message grouping in C++ compatibility mode

' to something else would have been via the 'qpid.default-message-group' queue declare argument when using an AMQP client to create the queue originally, and for 0.22 itself only that and the system property approach I mentioned would work. Robbie On 8 January 2014 04:03, Helen Kwong helenkw

Re: Possible optimizations in Java client to reduce memory footprint

/browse/QPID On 7 May 2013 03:10, Helen Kwong helenkw...@gmail.com wrote: Hello, My team is using the Java broker and Java client, version 0.16, and looking to lower the client's memory footprint on our servers. We did some heap analysis and found that the consumption is coming mostly

Possible optimizations in Java client to reduce memory footprint

Hello, My team is using the Java broker and Java client, version 0.16, and looking to lower the client's memory footprint on our servers. We did some heap analysis and found that the consumption is coming mostly from AMQAnyDestination instances, each having a retained size of 2864B, and since we