It worked!
It never occurred to me that the cursor memory high water mark can be set to
a value higher than 100.
The producers would only receive the exception if the messages they're
sending are persistent. But that would be a simple change on their end. At
least now my broker would be able to
It should work for non persistent also. Maybe they need alwaysSyncSend
On 26 Mar 2014 08:30, tikboy tikboy.balat...@gmail.com wrote:
It worked!
It never occurred to me that the cursor memory high water mark can be set
to
a value higher than 100.
The producers would only receive the
Actually what I would like is when the memoryLimit for a certain queue is
reached (even if it is set to 70%), the data should not be offloaded to any
store (memory, kahadb, temp) and for the producers to know that an exception
has happened so they could handle for themselves.
What is currently
set the cursor high water mark to 110, so it will not be reached
because pfc will kick in first.
then set systemUsage sendFailIfNoSpace=true and the producers will
get an exception when the memory limit is exceeded.
With this setup the default store cursor will be have like a vm cursor.
On 25
You need to change cursorMemoryHighWaterMark from the default 70% to
100% to ensure you reach your memory limit.
the file cursor will spool to disk when cursorMemoryHighWaterMark is
reached, so you won't reach the memory limit.
the (default) store cursor will stop caching at that value, so you
Hi,
I've configured a policy for my broker to have 20 mb memory limit for a
certain queue and the PFC turned off. I was expecting that when the memory
limit is reached, the client would be unable to publish messages to that
queue and would receive exceptions while sending a message.
But
