activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alainkr <>
Subject cursorMemoryHighWaterMark applies on the broker ? or policyEntry ?
Date Mon, 15 Jan 2018 19:14:17 GMT

I'm very puzzled by the cursorMemoryHighWaterMark after reading 
I tested lowering the highwater mark to prevent (or defer ) 100% memory

Using 5.10.0, with the setting 

I was excepting the limit to be per queue, but it's not ! It's global.
If one queue uses 25%, the other one will use up on 5%  max then swap go to

I this because of the wildcard ?

How can I express each queue to have a 30% watermark ? 


Sent from:

View raw message