Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Subject: Re: How to use INDIVIDUAL_ACKNOWLEDGE mode?
To: users@activemq.apache.org
References: 
 <CAEPS2V2OaGGB1AO77jPdR87S-niKxBYx9uGfscYGe9KQzSKnWw@mail.gmail.com>
From: Timothy Bish <tabish121@gmail.com>
Message-ID: <566752BD.10903@gmail.com>
Date: Tue, 8 Dec 2015 16:59:25 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: 
 <CAEPS2V2OaGGB1AO77jPdR87S-niKxBYx9uGfscYGe9KQzSKnWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 12/08/2015 04:44 PM, Camilo Rostoker wrote:
> Hi all,
>
> I'm trying to understand how to use the INDIVIDUAL_ACKNOWLEDGE mode
> properly.
>
> What I am trying to do is this:
>
> 1.  Message Producer sends messages to a queue
> 2.  Message Consumer receives individual message and confirms successful
> processing of each individual message.
> 3.  If Message Consumer cannot successfully process the message, then it
> should be re-delivered automatically according to the re-delivery policy.
>
>
> My question is this:  How is the _unsuccessful_ processing of a message
> communicated to the ActiveMQ broker?   The only way I've been able to do
> this is to explicitly throw some kind of RuntimeException, but this seems
> hacky.

Throwing is one option, otherwise closing the consumer will cause all
unack'd messages to be redelivered to another consumer. 

>
> I have almost been able to get this working using the transactional queue
> approach, to explicitly commit or rollback an individual message, but this
> then causes the message redelivery mechanism to re-send messages using
> incorrect schedule.
>
> Any help is greatly appreciated.
>
> Thanks!
> Cam
>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.redhat.com 
twitter: @tabish121
blog: http://timbish.blogspot.com/