Return-Path: 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 0F1F8CE5F for ; Wed, 6 Jun 2012 10:39:50 +0000 (UTC) Received: (qmail 62334 invoked by uid 500); 6 Jun 2012 10:39:49 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 62052 invoked by uid 500); 6 Jun 2012 10:39:49 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 62008 invoked by uid 99); 6 Jun 2012 10:39:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 10:39:47 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2012 10:39:43 +0000 Received: by qcsp15 with SMTP id p15so3445827qcs.2 for ; Wed, 06 Jun 2012 03:39:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XFt4oD8+P/noSzyMn/P03kfLULX4sIpHzeHGYH0ZQ68=; b=vrcpakvpE9sEIzt5+kCg8YOmGgiz0Jm6AZgiWcDl+sgjYEtb6KRZqdEs9bFszhN/l5 5AGHhobH1NzwAc+COpUwMKqOf0G/08+ISa1wrQxotLkN0w4dHihH4tjyL3weUDB/s3WX 19qNK0Su5O1z8bSl3xCX8va6l2KVnn+DMpmzE4ZK/PSvmHPlIiOPSOUfR5OeDQvZSR23 P7BH5szkqejmrcv4i0RbqKOrRtdipk/7ceTZxs3f0Ow6z4fDlfJxiVxNmPurg1OnIgHW IoUcpqFu6h1/bt9fw/9x8L8VB0mOQJX8w8RiJzC8gpJCxm/FcPvr5LJDKhQo75Qi2COY qL/A== MIME-Version: 1.0 Received: by 10.229.102.130 with SMTP id g2mr435268qco.77.1338979162162; Wed, 06 Jun 2012 03:39:22 -0700 (PDT) Received: by 10.229.13.8 with HTTP; Wed, 6 Jun 2012 03:39:22 -0700 (PDT) In-Reply-To: <1338976028201-4653014.post@n4.nabble.com> References: <1338554379639-4652919.post@n4.nabble.com> <1338976028201-4653014.post@n4.nabble.com> Date: Wed, 6 Jun 2012 11:39:22 +0100 Message-ID: Subject: Re: javax.jms.JMSException: Could not correlate acknowledgment with dispatched message: MessageAck From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org that is usually the result of failover reconnect. An ack is outstanding on the client and it gets sent after a reconnect. However the broker has not had a chance to redelivery/dispatch any messages, so the ack does not correspond to anything that has been dispatched. The messages either have not yet been dispatched or have been dispatched to another consumer. In the event that the messages are eventually dispatched to a new consumer on a different connection, they may be considered duplicates. If they are dispatched to the same consumer, the client side duplicate detection will trap them. If you want to guard against duplicate delivery in this case, you need to use a transacted session for your consumer. A transaction with an outstanding ack will fail if the messages are not redelivered to the same consumer. On 6 June 2012 10:47, OmkarBanawalikar wrote: > Can anyone tell me the cause of the above Exception, so that I can correct my > code. > > Thanks. > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/javax-jms-JMSException-Could-not-correlate-acknowledgment-with-dispatched-message-MessageAck-tp4652919p4653014.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com