networks of brokers in activemq are store and forward. So a persistent
message will only exist on one broker at a time.
If can start on the embedded broker and get forward to a networked
broker if there is demand, In which case it will be removed/consumed
from the embedded broker and sent to the ta
I have however also notice that persistent doesn't appear to handle
failover well when in a network of brokers setup. For instance say you
have 3 brokers with a consumer attached to each. All connected in a
persistent style. If broker 1 goes down and the consumer switches over
to broker 2. Any mess
If you think of persistence in the same way you would a POP3 store,
i.e the object of the persistence store is more to provide reliability in that
1: Write incoming message to disk,
2: Maintain a journal of actions taken to the message
3: Remove the message from the store once consumed.
So the
I am in the phase of imagining what using ActiveMQ to design a wrapper
around a legacy process would look like, and reading the book, which I
have bought. I should say that I am impressed so far with ActiveMQ and
the mapping of what it does with what I am trying to do seems very good.
I am tr
