activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: memoryLimit behavior (5.5.1)
Date Wed, 26 Mar 2014 10:08:20 GMT
It should work for non persistent also.  Maybe they need alwaysSyncSend
On 26 Mar 2014 08:30, "tikboy" <tikboy.balatong@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 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 survive and only that particular queue
> would be unresponsive.
>
> Thanks for the help!
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/memoryLimit-behavior-5-5-1-tp4679389p4679526.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message