Return-Path: 
 <users-return-28306-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BEC776E01
	for <apmail-activemq-users-archive@www.apache.org>;
 Wed, 27 Jul 2011 10:06:27 +0000 (UTC)
Received: (qmail 36516 invoked by uid 500); 27 Jul 2011 09:26:33 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 36090 invoked by uid 500); 27 Jul 2011 09:26:12 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 35466 invoked by uid 99); 27 Jul 2011 09:25:13 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2011 09:25:13 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2011 09:25:07 +0000
Received: from joe.nabble.com ([192.168.236.139])
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <pwanner@pwanner.com>)
	id 1Qm0MA-0006kV-GG
	for users@activemq.apache.org; Wed, 27 Jul 2011 02:24:46 -0700
Date: Wed, 27 Jul 2011 02:24:46 -0700 (PDT)
From: pwanner <pwanner@pwanner.com>
To: users@activemq.apache.org
Message-ID: <1311758686494-3697960.post@n4.nabble.com>
In-Reply-To: <1310999954343-3675465.post@n4.nabble.com>
References: <1305555175936-3526298.post@n4.nabble.com>
 <BANLkTi=M1Ec_RdeYv7+edSf=fKSPFoWz2A@mail.gmail.com>
 <1305633469265-3528960.post@n4.nabble.com>
 <1305805188131-3535464.post@n4.nabble.com>
 <1307694595524-3587855.post@n4.nabble.com>
 <1309870115281-3645856.post@n4.nabble.com>
 <CAH+vQmPk5Eq0YUSONQw6-4nsJABT+5MfhJ4g10nQjfgmZwHufw@mail.gmail.com>
 <1309942721135-3648087.post@n4.nabble.com>
 <1310368711813-3658836.post@n4.nabble.com>
 <1310999954343-3675465.post@n4.nabble.com>
Subject: Re: How does prefetch work with client acknoledgements?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi everybody,

I just had a server crash today and the slave ActiveMQ instance went active,
and a message is stuck in the queue. The new messages are consumed but there
is one that stays.

This is very annoying...

I use ActiveMQ 5.5.0 (same problem with 5.4.2) and Spring 3.0.5 as the
consumer.

Below is the config:

<jms:listener-container concurrency="5"
	destination-type="queue" 
	connection-factory="amqCachedConnectionFactory"
	transaction-manager="transactionManager"
	acknowledge="transacted" >
	<jms:listener destination="events" ref="eventHandler" />
</jms:listener-container>

<bean id="amqCachedConnectionFactory"
	class="org.springframework.jms.connection.CachingConnectionFactory"
	p:targetConnectionFactory-ref="amqConnectionFactory"
	p:sessionCacheSize="5" />

<amq:connectionFactory id="amqConnectionFactory" 

brokerURL="failover://(${broker.url.1},${broker.url.2})?jms.prefetchPolicy.all=1&amp;timeout=5000"
/>



--
View this message in context: http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-tp3244342p3697960.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.