Ok I will. By that time maybe you want to take a look at this post where I
explained the problem in more details.
http://www.nabble.com/Possible-defect-in-Message-Eviction-to22415827.html
http://www.nabble.com/Possible-defect-in-Message-Eviction-to22415827.html
Yannick
Andreas Gies-3 wrote:
>
Hi,
I am glad the answer helped a bit. It would be great if you could turn
your test app into a JUnit test and log a JIRA for your issue.
Best regards
Andreas
On Mar 11, 2009, at 9:27 PM, Yenki wrote:
Hi Andreas,
thanks for your help! We also managed to make memory limit work on
5.2. B
Hi Andreas,
thanks for your help! We also managed to make memory limit work on 5.2. But
we still have problemes with message eviction. I'v create a small
application to test it while stepping in ActiveMQ code. What I found is that
one evicted message out of two is redirected to the client. I'm al
Hi there,
I have run into a similar issue with a later version of ActiveMQ and
have blogged about that.
Perhaps that helps you:
http://open-source-adventures.blogspot.com/2009/01/limiting-disk-store-usage-with-active.html
Best regards
Andreas
On Mar 11, 2009, at 6:24 PM, pclovec wrote:
M
Make met same problem
Yenki wrote:
>
> Hi, for the last few days I’ve been trying to solve a fast producers /
> slow consumer problem. I want a limited amount of messages fetch on the
> consumer (this works) but I also want to have a limited amount of messages
> in the queue itself (doesn’t wor
Hi, for the last few days I’ve been trying to solve a fast producers / slow
consumer problem. I want a limited amount of messages fetch on the consumer
(this works) but I also want to have a limited amount of messages in the
queue itself (doesn’t work). I use ActiveMQ 4.1.2 Here is what I tried:
