You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Andrew L <kh...@hotmail.com> on 2010/02/17 22:17:53 UTC
Standard practice for recovering from resource exceeded exception
My system is sending messages asynchronously and they are enqueued much faster than they are dequeued. What is the standard method for handling a resource policy exceeded exception from the broker? Wait and retry sending after some time? Is there a more pro-active method?
Thanks.
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/201469230/direct/01/
Re: Standard practice for recovering from resource exceeded exception
Posted by Rajith Attapattu <ra...@gmail.com>.
On Wed, Feb 17, 2010 at 4:17 PM, Andrew L <kh...@hotmail.com> wrote:
>
> My system is sending messages asynchronously and they are enqueued much faster than they are dequeued. What is the standard method for handling a resource policy exceeded exception from the broker? Wait and retry sending after some time? Is there a more pro-active method?
Are you using the c++ client?
If so you would need to re-create your session and then retry after sometime.
However the following may help in eliminating blind retries
If you know the queue-limit then you could do a queue query and get
the current message count.
This will not be much of a help if you have exceeded the byte count
(as opposed to the message count) as the above doesn't give you the
byte depth.
>
> Thanks.
>
> _________________________________________________________________
> Hotmail: Powerful Free email with security by Microsoft.
> http://clk.atdmt.com/GBL/go/201469230/direct/01/
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org