Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.191.145.13
 which is an MX secondary for users@activemq.apache.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAAZU44m7_-m5DADwdENbuf3kGLFzvOHNYxt5=Jv-WOK29xcmGg@mail.gmail.com>
References: 
 <CAAZU44m7_-m5DADwdENbuf3kGLFzvOHNYxt5=Jv-WOK29xcmGg@mail.gmail.com>
Date: Wed, 22 Apr 2015 11:51:14 +0100
Message-ID: 
 <CAH+vQmNGB3LwLwvjJd=FpAtXNGyuZxJrP-eC4HeUBLpW7pBAyg@mail.gmail.com>
Subject: Re: Monitoring producer flow control.
From: Gary Tully <gary.tully@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

https://issues.apache.org/jira/browse/AMQ-4635 may lelp.
there is also a destination statistic for blocked sends that could be monit=
ored
and there is an advisory that fires when a dest is full.

On 17 April 2015 at 03:25, Kevin Burton <burton@spinn3r.com> wrote:
> I=E2=80=99m looking at implementing producer flow control so that I don=
=E2=80=99t fill up
> the queues on my broker.
>
> It doesn=E2=80=99t look like there=E2=80=99s any way I can see that a cli=
ent is blocking,
> waiting for resources to be released.
>
> Maybe one strategy could be to put a stopwatch around each send() and the=
n
> I can see that I have some outstanding that have been open for a long tim=
e.
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> =E2=80=A6 or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
> <http://spinn3r.com>