I did make sure of persistence both in XML and while sending message
[producer.setDeliveryMode(DeliveryMode.PERSISTENT)].
Its still getting lost after fail-over.
And I observed one more thing, after the fail-over, if I stop the active
broker it does not connect back to reinstated broker.
Flow:
B
Scenario:
I have five process: guard, watchdog, mdp, ems and security. Each process's
work is as follows:
Gurad: start an ActiveMQ server; monitor process watchdog, mdp, ems and
security, restart these process if they shutdown abnormally.
Watchdog: monitor process guard, restart it if it shutdown a
Hello,
I am very new to this forum and I am hoping that you all will see this email.
Currently I am testing the following setup:
ActiveMQ 5.13.0 with LevelDB (3 node cluster).
Zookeeper 3.4.6 (3 node cluster).
Started up all 3 Zookeeper nodes.
Started up all 3 ActiveMQ nodes.
As I started a
thank you again
--
View this message in context:
http://activemq.2283324.n4.nabble.com/how-to-set-the-number-of-message-that-topic-keeped-tp4706628p4706706.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I think Clebert covered the fact that no one's going to give you an
official statement of guaranteed support; if you want that, contact one of
the vendors who offer that and get a quote. But since we're an open-source
project with a publicly visible issue tracking system, if there's an issue
you r
Yes, a single broker can support many clients, so once you have one (that
will be online whenever any of the clients will want to connect to it), you
don't have to have one for the clients. There are sometimes reasons that
people would want to do that (primarily because it decouples the client
fro
Hi Robbie,
Thanks for taking the time to reply!
As I mentioned, I'm new to this subject, therefore I have no idea as to the
AMQP architecture.
One more question if I may..
As far as I understand it, I need to have only one Broker and it will be
accessed by several clients - is that right ? I mean
