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 raul@fusesource.com
 designates 209.85.214.171 as permitted sender)
Mime-Version: 1.0 (1.0)
References: <1344550007327-4654986.post@n4.nabble.com>
In-Reply-To: <1344550007327-4654986.post@n4.nabble.com>
From: Raul Kripalani <raul@fusesource.com>
Date: Fri, 10 Aug 2012 09:36:00 +0100
Message-ID: <-8690331837731399482@unknownmsgid>
Subject: Re: Request Redelivery of Acknowledged Messages
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Not that I know of. Once acked, the broker can safely forget about
that message. Allowing a broker to store messages perpetually would
defeat the purpose of a messaging broker and turn it into a database.

Here's a post that dives deep into consumer acks. You may find it
useful: http://blog.raulkr.net/2012/08/consumer-acknowledgements-in-activem=
q.html?m=3D0.

And here's another post by Dejan about the messaging anti-pattern of
using the broker as a DB:
http://sensatic.net/messaging/messaging-anti-patterns-part-1.html.

Hope that helps,
Ra=FAl Kripalani.

On 9 Aug 2012, at 23:07, fenbers <Mark.Fenbers@noaa.gov> wrote:

> Is there a way for my client app to request redelivery of unexpired messa=
ges
> that my client has already acknowledged in a previous instance?
> Session.recover() will only resend un-acknowledged messages.
> Mark
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Reque=
st-Redelivery-of-Acknowledged-Messages-tp4654986.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.