misunderstanding was that I thought Flow Control would
kick in with the per-queue memory limit rather than paying attention to the
temporary storage!
Thanks very much for your replies.
On Tuesday, June 11, 2013, Jesus Roncero wrote:
Hi,
Any extra info on this?
Regards
On Fri, Jun 7, 2013
Hi,
Any extra info on this?
Regards
On Fri, Jun 7, 2013 at 12:11 PM, Jesus Roncero je...@we7.com wrote:
On Thu, Jun 06, 2013 at 08:34:03AM -0700, Christian Posta wrote:
When you have producer flow control enabled, your producers should block
when you've reached the memory limits (50mb
On Thu, Jun 06, 2013 at 08:34:03AM -0700, Christian Posta wrote:
When you have producer flow control enabled, your producers should block
when you've reached the memory limits (50mb). If you can write a unit test
that shows otherwise, I would gladly take a look.
Hi Christian,
again thanks for
On Wed, Jun 05, 2013 at 09:03:15AM -0700, Christian Posta wrote:
was just thinking... for question #3, it would make sense if the overall
broker memory was 500MB and your temp was 100MB... then when you hit the
cursor high water mark at some point (70%) it would spook to disk and
overload the
On Wed, Jun 05, 2013 at 08:57:01AM -0700, Christian Posta wrote:
Hi,
further on this:
Sounds like it's happening exactly as you have it configured.. I assume
you're using non-persistent messages?
As Johan pointed out, your config kinda doesn't make sense :)
The memoryUsage is an overall
On Thu, Jun 06, 2013 at 07:45:30AM -0700, Christian Posta wrote:
Oh I see... because you have producer flow control turned off. The memory
limits won't be taken into account, even when their full. You would have to
plan around that in subsequent configuration details, in this case you're
using
