Hi,
I'd say you are running into flow control.
http://activemq.apache.org/producer-flow-control.html
With configuration you can achieve that you get an exception if your
storage is full, for example:
|<systemUsage>|
|||<systemUsage sendFailIfNoSpace="||true||">|
|||<memoryUsage>|
|||<memoryUsage limit="||20| |mb"/>|
|||</memoryUsage>|
|||</systemUsage>|
|</systemUsage>
You can also decide to throw the exception only after a given timeout,
so your producers would wait a bit
whether space becomes available again and only throw the exception if
the timeout is exceeded.
Hope that helps
Andreas
|
On 08/10/14 08:16, harlo wrote:
Hi,
I have an application in java with a failover configuration like this:
failover://(tcp://someip:61616,tcp://otherip:61616)?timeout=100&randomize=false&maxReconnectAttempts=2
but when kahadb reaches the limit of its storage the producers just keep
waiting.
The implementation in the client side at first was with spring and hope to
get different results with pure java but when we hit this scenario i
expected to get an exception, reach the next broker or something but its the
same with both approaches.
Any idea?
Thanks in advance
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Kahadb-reach-storage-limit-then-producers-turn-idle-tp4686219.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Andreas Gies
WoQ -- Way of Quality GmbH
Geschäftsführer & CTO
/eMail:/andr...@wayofquality.de <mailto:andr...@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.
//
