activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garner, Shawn" <>
Subject RE: DefaultMessageListenerContainer + not remove messages until processed
Date Wed, 04 Apr 2007 16:09:57 GMT
I put a org.springframework.jms.connection.JmsTransactionManager on the
DefaultMessageListenerContainer but all this does is roll back any
changes I made after consuming the message. 

I am also using the org.jencks.factory.TransactionManagerFactoryBean and
org.jencks.factory.ConnectionManagerFactoryBean since I'm in Tomcat
without any EJB layer.

It does not put the message back into the queue like I want.

How do you enable client-acknowledge mode?

-----Original Message-----
From: James Strachan [] 
Sent: Wednesday, April 04, 2007 11:01 AM
Subject: Re: DefaultMessageListenerContainer + not remove messages until

Try using transacted mode and Spring transactions, or using
client-acknowledge mode.

On 4/4/07, Garner, Shawn <> wrote:
> I would like the message queue to keep the message until I am finished
> with processing and explicitly tell it the message can be removed.
> I'm using
> org.springframework.jms.listener.DefaultMessageListenerContainer to
> deliver the message to a POJO but it seems once the message is
> it is out of the queue.
> So now if I shut down the java vm running the broker the message has
> already been consumed and does not get delivered when the vm is
> backup again.
> Can somebody tell me some approaches to doing this?
> All my ActiveMQ settings, POJO consumer, POJO producer are in a spring
> context file loaded when the web-application starts.
> Shawn



View raw message