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: domain of gary.tully@gmail.com
 designates 209.85.216.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1392826008033-4678153.post@n4.nabble.com>
References: <1392809852232-4678120.post@n4.nabble.com>
	<1392826008033-4678153.post@n4.nabble.com>
Date: Wed, 19 Feb 2014 23:04:05 +0000
Message-ID: 
 <CAH+vQmNAqDb4YZ_GDqcwwpRSFM6HDXZ-Rif3S3cGPWN=roKb-g@mail.gmail.com>
Subject: Re: Client side producer flow control exception never thrown
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=047d7bdc7810cccd9c04f2ca6765

--047d7bdc7810cccd9c04f2ca6765
Content-Type: text/plain; charset=ISO-8859-1

It looks like you are using async send so there is nothing to trap any
exception.
On 19 Feb 2014 16:07, "James Black" <be_strew@yahoo.co.uk> wrote:

> After clearing down the queues using the admin console I can see that the
> store percent used is back to zero.  However, this did not cause the
> blocking in our application to exit.
>
> After restarting our applications but not ActiveMq they were still blocked
> and unable to receive API requests.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Client-side-producer-flow-control-exception-never-thrown-tp4678120p4678153.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

--047d7bdc7810cccd9c04f2ca6765--