Return-Path: 
 <dev-return-23636-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 58675 invoked from network); 2 Dec 2010 13:11:40 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 2 Dec 2010 13:11:40 -0000
Received: (qmail 7548 invoked by uid 500); 2 Dec 2010 13:11:39 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 7497 invoked by uid 500); 2 Dec 2010 13:11:39 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 7362 invoked by uid 99); 2 Dec 2010 13:11:39 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 13:11:39 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 13:11:37 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB2DBFrq003926
	for <dev@activemq.apache.org>; Thu, 2 Dec 2010 13:11:15 GMT
Message-ID: <13361445.70291291295475903.JavaMail.jira@thor>
Date: Thu, 2 Dec 2010 08:11:15 -0500 (EST)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2373) Expired Messages appear through policy
 entry on the DLQ and are also processed from the main Queue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/AMQ-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac updated AMQ-2373:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> Expired Messages appear through policy entry on the DLQ and are also processed from the main Queue
> --------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2373
>                 URL: https://issues.apache.org/jira/browse/AMQ-2373
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Andrew Maharaj
>             Fix For: 5.5.0
>
>
> Hi,
> We have a policy entry like this:
> <destinationPolicy>
>                 <policyMap>
>                                  <policyEntries>
>                                                   <policyEntry queue=">" memoryLimit="10mb">
>                                                                   <deadLetterStrategy>     
>                                                                                 <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" />     
>                                                                 </deadLetterStrategy>     
>                                                   </policyEntry>
>                                                   <policyEntry topic=">" memoryLimit="10mb">
>                                                   </policyEntry>
>                                  </policyEntries>
>                 </policyMap>
> </destinationPolicy>
> Messages sent with an expiry time of 10 seconds appear on the Dead Letter Queue.
> However, if a Message Driven Bean ultimately picks up the message from the main queue in a transaction and the transaction is slow, the message can expire while the transaction is in progress.
> This leads to a situation where the message is processed twice, implying that the queue processing is not atomic.
>                         - The main MDB completes processing, 
>                         - The expired message is moved to the DLQ 
>                         - The MDB listening to the Dead Letter Queue also processes a response.
> Utlimately, responses for the expired message and for the in flight message are both generated.  Neither operation reports any exceptions.
> The MDB's are simple, vanilla MDB's using Apache Geronimo 2.1.4 and referring to a separate ActiveMQ 5.2 installation (not the 4.1 shipped with Geronimo).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.