The broker will create the log files and periodically checkpoint status to them even if no messages are being written to them.
Furthermore, sending non-persistent messages to an HA broker does not make much sense because the only messages that are HA, and get recovered on failure, are the persistent messages. For what you are doing you might as well just run 2 brokers that are NOT in HA configuration, use normal network connections between them and configure the clients to failover between them. The client will not notice the broker failure, you will get load balancing between the 2 brokers. and you still get the same QoS on the messages which is you might loose a few messages when a broker dies. On Dec 10, 2007 4:47 AM, hagai <[EMAIL PROTECTED]> wrote: > > That's exactly what I tried to do. I mark all the messages as non persistent > using messageProducer.setDeliveryMode(DeliveryMode.NON_PERSISTENT) > but it seems that the broker does use persistency on these messages because > the log files are updated. > Am I missing something? > > Hagai. > > > -- > View this message in context: > http://www.nabble.com/High-availability-and-persistency-tp14240560s2354p14249961.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
