activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Monitoring producer flow control.
Date Fri, 17 Apr 2015 12:10:01 GMT
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" <tbain@alumni.duke.edu> wrote:

> 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" <burton@spinn3r.com> wrote:
>
>> 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 that I have some outstanding that have been open for a long
>> time.
>>
>>
>> --
>>
>> Founder/CEO Spinn3r.com
>> Location: *San Francisco, CA*
>> blog: http://burtonator.wordpress.com
>> … or check out my Google+ profile
>> <https://plus.google.com/102718274791889610666/posts>
>> <http://spinn3r.com>
>>
>

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