ok, so hypothetically if we had 1 queue. then there should be no out of
memory errors using that configuration?
also this causes us issues anyway as we have a solution that has an unbound
potential number of queues on the system. so we cannot judge the appropriate
value to set for the destination
70% is the magic number, there is a cursorHighWaterMark destination policy
that defaults to 70% of system usage. your config can go to 80%
On 7 April 2010 12:15, Richard Holt wrote:
>
> Hi Gary,
>
> It appears i am really not understanding this so could you clarify?
>
> You wrote:
>
> "Which eve
Hi Gary,
It appears i am really not understanding this so could you clarify?
You wrote:
"Which ever destination tips it over the limit will have its memory usage
flushed to disk because it is
configured with a fileQueueCursor."
and then wrote:
"The salient point being that paging to disk is
richard, you have configured a 1mb limit for every queue because you use the
">". So the broker will keep up to 1mb of space in memory for each queue, up
to 16MB for 16 queues.
The paging (via fileQueueCursor) kicks in for each destination only when 70%
of the shared system limit (20mb) is reached
Sorry about the thread hijack - however if i have something like this
Some answers in line:
On 2 April 2010 17:47, dcheckoway wrote:
>
> Thanks Gary. So lemme toss some actual config numbers out there and please
> tell me if this makes any sense...or if I'm shooting myself in the foot
> somehow:
>
> Destinations:
> - 1 queue with very heavy use, say 50 million mes
i am also interested in the answers to this please if anyone can help, the
documentation surrounding this is a bit spartan...
dcheckoway wrote:
>
> Thanks Gary. So lemme toss some actual config numbers out there and
> please tell me if this makes any sense...or if I'm shooting myself in the
>
Thanks Gary. So lemme toss some actual config numbers out there and please
tell me if this makes any sense...or if I'm shooting myself in the foot
somehow:
Destinations:
- 1 queue with very heavy use, say 50 million messages per day
- 1 queue with very light use, say up to 500 messages per day
-
On 2 April 2010 12:30, dcheckoway wrote:
>
> I could use some help understanding memory usage & limits in activemq.
> 5.3.1
> is what I'm running, fwiw.
>
> 1. Out of the box, in activemq.xml is commented out. I'm
> passing ACTIVEMQ_OPTS="-Xmx2048M ...". What is the default behavior in
> that
