Requirements to ensure no message loss in master/slave configuration

[ariekenb <aa...@lmco.com>]

Suppose I have the following situation:

incoming messages on JMS queues -> bean processor (business logic) ->
outgoing messages on JMS queues

I have this all running on ServiceMix 4, which includes ActiveMQ 5.1.  I'm
injecting messages into the bean processor using the Camel bean component to
inject into a method in the bean processor.  Then I'm using an injected
Camel ProducerTemplate in the bean processor to send to outgoing queues,
based on the results of the business logic.

For reliability, I'd like to run this all as a MasterSlave, probably using
the shared filesystem approach.  From an ActiveMQ perspective, what is
needed to ensure there is no message loss?  I assume all messages on all
queues must be persistent.  I'm wondering if I also need to use
transactions, or if auto-acknowledge is sufficient.

Can I really be 100% certain in this situation that no messages will ever be
lost if a master fails and a slave takes over?
-- 
View this message in context: http://www.nabble.com/Requirements-to-ensure-no-message-loss-in-master-slave-configuration-tp21457137p21457137.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.