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: Kahadb reach storage limit then producers turn "idle"
Date Thu, 09 Oct 2014 15:39:36 GMT
In addition to using timeouts, you can also configure the broker to discard
messages when more than a certain number are pending, to avoid blocking
producers; see http://activemq.apache.org/slow-consumer-handling.html for
more details.

On Thu, Oct 9, 2014 at 2:59 AM, Andreas Gies <andreas@wayofquality.de>
wrote:

> Glad to be of help. If you say "switch to the slave" you don't actually
> mean a slave
> in a master/slave pair ? - If so you are slightly on the wrong track as
> the slave won't
> be active  at this point in time and not available for messaging.
>
> In my applications i usually sit down with the end users and try to
> determine the max
> number of messages that shall be buffered and size my store very
> carefully. I also work
> with message TTL's, subscription timeouts and similar things to make sure
> that messages
> don't pile unnecessarily.
>
> Usually that works very well and I have not come across the requirement of
> switching to
> another broker to send messages so far.
>
> Best regards
> Andreas
>
>
> On 09/10/14 00:11, harlo wrote:
>
>> Thank you so much Andreas!
>>
>> It seems to work fine, now I'm getting a ResourceAllocationException in
>> the
>> client side, that allow me to continue with the process.
>>
>> Now i need to find out if the client can switch automatically and send the
>> msg to the slave broker.
>>
>> Thank you for your quick and helpful answer.
>>
>> Best regards
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://activemq.2283324.n4.
>> nabble.com/Kahadb-reach-storage-limit-then-producers-
>> turn-idle-tp4686219p4686244.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> --
>
>
>    Andreas Gies
>
> WoQ -- Way of Quality GmbH
>
> Geschäftsführer & CTO
>
> /eMail:/andreas@wayofquality.de <mailto:andreas@wayofquality.de>
>
> /Tel:/ +49 151 23470823
>
> /Fax:/ +49 1805 006534 2114
>
> /Twitter:/ andreasgies /Skype:/ giessonic
>
> /LinkedIn:/ <http://de.linkedin.com/pub/andreas-gies/0/594/aa5/> (
> http://de.linkedin.com/pub/andreas-gies/0/594/aa5/)
>
> /Xing:/ <http://www.xing.com/profile/Andreas_Gies> (
> http://www.xing.com/profile/Andreas_Gies)
>
> /Blog:/ <http://www.wayofquality.de/index.php/en/blog> (
> http://www.wayofquality.de/index.php/en/blog)
>
> /Github:/ <https://github.com/atooni> (https://github.com/atooni)
>
> /Amtsgericht Landshut:/HRB 8352//
>
> //
>
> /Ust.-Id.:/ DE274771254
>
>
>      Haftungsausschluss
>
> Diese Email kann vertrauliche und/oder rechtlich geschützte Informationen
> enthalten und ist ausschließlich für den/die benannten Adressaten bestimmt.
> Sollten Sie nicht der beabsichtigte Empfänger sein oder diese Email
> irrtümlich erhalten haben, ist es Ihnen nicht gestattet diese Mail oder
> einen Teil davon ohne unsere Erlaubnis zu verbreiten, zu kopieren, unbefugt
> weiterzuleiten oder zu behalten. Informieren Sie bitte sofort den Absender
> telefonisch oder per Email und löschen Sie diese Email und alle Kopien aus
> Ihrem System. Wir haften nicht für die Unversehrtheit von Emails, nachdem
> sie unseren Einflussbereich verlassen haben.
>
>
>      Disclaimer
>
> This email may contain confidential and/or privileged information and is
> intended solely for the attention and use of the named addressee(s). If you
> are not the intended recipient, or a person responsible for delivering it
> to the intended recipient, you are not authorized to and must not disclose,
> copy, distribute, or retain this message or any part of it without our
> authority. Please contact the sender by call or reply email immediately and
> destroy all copies and the original message. We are not responsible for the
> integrity of emails after they have left our sphere of control.
>
> //
>

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