https://issues.apache.org/jira/browse/AMQ-5741
On Wed, Apr 22, 2015 at 7:12 AM, Tim Bain wrote:
> And of course both of those are documented at
> http://activemq.apache.org/jmx.html... Er, nope, that page hasn't been
> updated in ages, despite new features like these being added.
>
> How can we
And of course both of those are documented at
http://activemq.apache.org/jmx.html... Er, nope, that page hasn't been
updated in ages, despite new features like these being added.
How can we improve the process to increase the likelihood that JMX changes
make it onto the webpage? Maybe a post-com
https://issues.apache.org/jira/browse/AMQ-4635 may lelp.
there is also a destination statistic for blocked sends that could be monitored
and there is an advisory that fires when a dest is full.
On 17 April 2015 at 03:25, Kevin Burton wrote:
> I’m looking at implementing producer flow control so t
there is a way to check the destination to see if PFC is enabled by
checking the JMX:
https://github.com/apache/activemq/blob/master/activemq-broker/src/main/java/org/apache/activemq/broker/jmx/DestinationView.java#L423
On Thu, Apr 16, 2015 at 7:25 PM, Kevin Burton wrote:
> I’m looking at impl
Yes. The way I was going to do it was have a gauge that measures how long
blocking calls are open for.
I’ll see it in our monitoring system because all of a sudden the send
latencies will keep rising per second.
On Fri, Apr 17, 2015 at 5:10 AM, Tim Bain wrote:
> Also keep in mind that send() i
Ah. yeah. I just saw that. I wrote a test for it and it triggered the log
line. I might look at that line and try to figure out the best way to
track that? Maybe a JMX integer that’s integrated for each time it
happens?
I might not need it in the short term but probably will in the long term.
I
Also keep in mind that send() is a blocking call, so the stopwatch idea
will only tell you when PFC has occurred and then cleared up (once send()
returns), but won't alert you to a deadlock that won't clear up on its own.
On Apr 17, 2015 6:06 AM, "Tim Bain" wrote:
> There's a log line in the brok
There's a log line in the broker whenever PFC kicks in; we watched the logs
for that line and fire off an email to get someone to investigate. Would
that meet your needs?
On Apr 16, 2015 10:10 PM, "Kevin Burton" wrote:
> I’m looking at implementing producer flow control so that I don’t fill up
>
I’m looking at implementing producer flow control so that I don’t fill up
the queues on my broker.
It doesn’t look like there’s any way I can see that a client is blocking,
waiting for resources to be released.
Maybe one strategy could be to put a stopwatch around each send() and then
I can see t
