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.216.176 as permitted sender)
MIME-Version: 1.0
Sender: chirino@gmail.com
In-Reply-To: <405AAADA-B8F3-4D65-B3F8-FA79310B3E3F@w007.org>
References: <405AAADA-B8F3-4D65-B3F8-FA79310B3E3F@w007.org>
Date: Thu, 15 May 2014 09:51:07 -0400
Message-ID: 
 <CAGZ-RDKUbJtJ1wHqw9ttJPX-EGvxfKMGWPd8cuQT=+GWNxshAQ@mail.gmail.com>
Subject: Re: Use message selectors against messages on disk
From: Hiram Chirino <hiram@hiramchirino.com>
To: users <users@activemq.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Using selector should work regardless if the message is on disk or in
memory.. If it's not then it's a bug.  Do you have a test case showing
it's broken?

On Tue, May 13, 2014 at 12:28 PM, Benjamin Jansen
<bjansen-activemq@w007.org> wrote:
> Hello,
>
> In ActiveMQ 5.x (I have tried 5.6.0 and 5.9.1), is it possible to use JMS=
 message selectors against in-flight messages that have been put on disk? B=
ased on my experimentation, it appears not, but I wanted to double-check, s=
ince I've found conflicting information on the Web.
>
> A comment on a blog post describing this behavior, claims that it has bee=
n fixed: http://bit.ly/1sJpdw4
>
> OTOH, this issue seems to indicate that it will never be fixed in AMQ: ht=
tps://issues.apache.org/jira/browse/AMQ-2217
>
> Thanks for any insight.
>
> - Ben Jansen
>


--=20
Hiram Chirino
Engineering | Red Hat, Inc.
hchirino@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino