Ahh, now I understand the confusion, because I had to re-read that section
of the web page when I read it the first time.
All of that information is only in the context of the pending message limit
strategies described above it; if you've specified one of them (which must
be done manually; that's
http://activemq.apache.org/slow-consumer-handling.html
> We have a MessageEvictionStrategy which is used to decide which message
should be evicted on a slow consumer.
I’m also unclear why / if this is happening. If I have a slow consumer I
definitely don’t just want messages being removed from my
Are you talking about message expiration? Or do you have another
definition for message eviction that I'm not thinking of?
On Sun, Mar 1, 2015 at 3:24 PM, Kevin Burton wrote:
> Does the same apply to evictions?
>
> If I have messages begin evicted by ActiveMQ I definitely want to know it!
> :)
Does the same apply to evictions?
If I have messages begin evicted by ActiveMQ I definitely want to know it!
:)
On Sun, Mar 1, 2015 at 2:07 PM, Kevin Burton wrote:
> Cool!
>
> I think broker level at a minimum but I imagine having both on the
> destination level would be good too.
>
> https:/
Cool!
I think broker level at a minimum but I imagine having both on the
destination level would be good too.
https://issues.apache.org/jira/browse/AMQ-5624
On Sun, Mar 1, 2015 at 1:59 PM, Tim Bain wrote:
> This sounds like a useful feature; submit an Enhancement in JIRA for it...
>
> Were y
This sounds like a useful feature; submit an Enhancement in JIRA for it...
Were you looking for a broker-level count (count of slow consumers on all
destinations) or a destination-level count? Or both? (Implementing both
seems most useful to me, and not particularly hard to do.)
Tim
On Sun,
According to this:
http://activemq.apache.org/jmx.html
There are no simple metrics for the number of slow consumers.
Is there an easy way to figure this out?
Would be nice for monitoring systems so that alerts can be triggered.
Right now you have to enumerate each subscriber but it takes 200ms
