Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates
 209.85.198.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=YrhRD/0OF38/lfLAmVpYdbtGrSBj+oRmV5NQ1q7NiblP6CEvIYdIkJckuA0IIkibFGWIVpgNM7S8pPEwgDJjg65jVeEdXboZVQ/Nnws79Sy6ySaKZNqco6iFGAC1l3x3Cbo9UxAojZB9mVKaDa5ItdtKifeEiFbqxj2l0GJbMis=
Message-ID: <af2843cd0712141102t2138dea8j1f8fb434097dfc82@mail.gmail.com>
Date: Fri, 14 Dec 2007 14:02:50 -0500
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: users@activemq.apache.org
Subject: Re: High availability and persistency
In-Reply-To: <14249961.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <14249961.post@talk.nabble.com>

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 <hagai@liveperson.com> 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