Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.160.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=T+S1Xi8gma3GaDJkE6tps/Wuyfm+FT4G8QLJXbqgg2rYc0epDlwJZAAMQ2X4KROFsB
         O2gG0wc2SLg0DI9RuPuD+CWzRM8n5k/BWloPVs4wevw+oIWknCP5zULcBJTeDmczYZ29
         36FX8JFzeUQaF5vsCLtGX7U1CNpKwvU9U1JXw=
MIME-Version: 1.0
In-Reply-To: <9C408626-C3E2-4346-9CD4-2CF4C20D8C1D@homeaway.co.uk>
References: <9C408626-C3E2-4346-9CD4-2CF4C20D8C1D@homeaway.co.uk>
Date: Mon, 1 Nov 2010 09:32:55 +0000
Message-ID: <AANLkTinAL-GKYtQWhq=ukJbxy+vaq6_4nb25JXwHQ5A2@mail.gmail.com>
Subject: Re: Virtual Topic and missed messages gone missing with
 selectorAware=true
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Message expiry may help in the short term, set a time to live on the
messages such that the built up unmatched messages expire and are
removed.

On 1 November 2010 09:20, Maciej Rakowicz <maciek@homeaway.co.uk> wrote:
> All,
>
> amq 5.4.0. jdk 1.6
>
> Scenario:
> broker persistence=true, selectorAware=false
> Virtual Topic with say one queue. There is a consumer A connected to that
> queue with a selector. All works fine. Consumer A dies, messages pile up,
> consumer A starts back up, missed messages are redelivered. You can easily
> verify that queue receives all posted messages while consumer's down.
> Now, adding consumer B, since selectorAware=false and consumer B uses an
> exclusive selector messages sent to consumer A are not consumed by consumer
> B. All good save the fact that all unmatched messages end up polluting
> consumer's B queue. All according to the documentation.
> Flipping selectorAware to true solves one problem but introduces another
> (way more important in my setup). Unmatched messages won't pile up on
> consumer's B queue which is fine. However, if consumer A dies they are not
> sent to consumer's A queue (disappearing after reaching the topic - I dunno
> where they go) hence disabling any missed message delivery on consumer's A
> startup.
>
> I there any way around it? I really need to handle all missed messages with
> no exception. At the same time I cannot allow stacking up messages in each
> and every queue although they are not matched.
>
> Btw. I do not have a list of consumers in advance, the subscription is fully
> dynamic, although since broker runs persistence, once subscribed I do have
> an idea of who's subscribed even if connection is currently down.
>
> I would appreciate any hints.
>
> mac


-- 
http://blog.garytully.com
http://fusesource.com