Unfortunately we didn't receive any replies. We ended up moving to Kafka
(http://incubator.apache.org/kafka/) which suited our throughput and
availability use cases better.
-Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Async-error-occurred-Can-not-remove-a-
Hi hodgesz:
Did you ever get any useful replies or otherwise fix this problem? I am also
experiencing the exact same thing with a pure master/slave configuration.
TIA,
Mike (aka, patzerbud)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Async-error-occurred-Can-not-r
Hi Nag,
I have a very similar problem as the guy above and was wondering if you
think those links can also apply to my problem. I have read Bruce's blogs
but wasn't completely clear what to do. Do I have to setup a network of
brokers and shared database in order to take advantage of those settin
I had come across it and that topic is about network of brokers.
The warning message I am trying to solve is in case of just one broker.
I am using failover protocol just to reconnect to broker in case it goes
down and becomes available later.
But when I restart my client (spring app on j2ee serve
Please have a look at "updateClusterClients", "updateClusterClientsOnRemove"
Bruce Snyder's Blog may also help you::
http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-automatic.html
New Features in ActiveMQ 5.4.x
http://bsnyderblog.blogspot.com/2010/01/how-to-use-automatic-
