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 e.semog@gmail.com designates
 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=gZG7FOG/HqAm6UR3QeoTIgUpidMszz4jDmcRXs/8ZoVpR+D38scpznEVAVmkVT3+KGxqwp8pnfZEAlHVTqFOmUmnjSczcaQEGUuqjefIac01DZfOE7d8uJONqjsAnXMlQmWFqK1HMB4uKpIzGjjGUdIzFrHX/SeX4KLqLcbXXqc=
Message-ID: <5a56ce1b0802260722h660685d1r24aeef4f36e7dbcd@mail.gmail.com>
Date: Tue, 26 Feb 2008 07:22:47 -0800
From: "Jim Gomes" <e.semog@gmail.com>
To: users@activemq.apache.org
Subject: Re: Ordering of persistent/non-persistent messages in ActiveMQ 5
In-Reply-To: <3D246B80-588E-4343-B827-C49713E76DFD@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_18518_3740591.1204039367868"
References: <44cb1ba30802252249t228ddeffpfdbecb31353d9959@mail.gmail.com>
	 <3D246B80-588E-4343-B827-C49713E76DFD@gmail.com>

------=_Part_18518_3740591.1204039367868
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Rob,

Is this the same thing as the Total Ordering feature (c.f.,
http://activemq.apache.org/total-ordering.html), or is it something
different?  While it may be expected behavior, it was a little surprising to
read that was what would happen.

Best,
Jim

On Tue, Feb 26, 2008 at 12:06 AM, Rob Davies <rajdavies@gmail.com> wrote:

>
> On 26 Feb 2008, at 06:49, Roger Hoover wrote:
>
> > Using STOMP on AMQ 5, if I enqueue some persistent and non-persistent
> > messages and then consume them, they don't get consumed in the order
> > in
> > which they were produced.  The non-persistent messages are delivered
> > first
> > (with their relative order preserved) followed by the persistent
> > messages
> > (also with their relative order preserved).
> >
> > AMQ 4 preserved message order regardless of persistence settings.
> >
> > Is this expected behavior?  Is it controlled by any configuration?
> >
> > Thanks,
> >
> > Roger
>
> This is expected behaviour - as persistent/non-persistent messages
> have different qualities of service and take different paths through
> the broker
>
>

------=_Part_18518_3740591.1204039367868--