Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates
 209.85.216.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:in-reply-to:references:content-type:date:message-id
         :mime-version:x-mailer:content-transfer-encoding;
        b=WL0OGHz3DCqys/Z0VVYBPNPl2g+h4lpZrjWqrt+Y31W793jdJUWwbXx+ohCFJFO6t2
         1qxO6wBBcYDRwZWSkggzl1TQaHJpUjqnBSD7k7OZ4oslHMcvtS+YXf9gcyFMahwIjmfy
         zimNi0SY5mTG7ISWSMt1gaIf3327lnMf4psZ0=
Subject: Re: NMS 1.5 client not recognizing expired messages
From: Timothy Bish <tabish121@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <1300220247835-3357650.post@n4.nabble.com>
References: <1300220247835-3357650.post@n4.nabble.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 15 Mar 2011 16:45:34 -0400
Message-ID: <1300221934.2713.22.camel@office>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2011-03-15 at 13:17 -0700, TheFarmer wrote:
> I have a .NET consumer listening for messages.  The operation fails and
> message is rolled back and retries.  This happens over and over and I'm
> happy with that.  But eventually the time to live expires and I expect the
> retrying to stop.
> 
> What happens is the ActiveMQ server does push this message into the DLQ but
> the client did not notice this and it keeps retrying.  This also results in
> repeated errors in the activemq.log:
> 
> 2011-03-15 11:05:33,446 | WARN  | ignoring ack MessageAck {commandId =
> 14875, responseRequired = false, ackType = 2, consumerId =
> ID:abc-05-4864-634357153348730772-1:0:2:1, firstMessageId =
> ID:abc-05-4864-634357153348730772-1:0:3:1:1, lastMessageId =
> ID:abc-05-4864-634357153348730772-1:0:3:1:1, destination =
> queue://bms.GetBatchResponse, transactionId =
> TX:ID:abc-05-4864-634357153348730772-1:0:1922, messageCount = 1}, for
> already expired message: Message ID:abc-05-4864-634357153348730772-1:0:3:1:1
> dropped=true acked=true locked=false |
> org.apache.activemq.broker.region.QueueSubscription | ActiveMQ Transport:
> tcp:///234.11.234.101:4865
> 
> The same this happens when the message on the activeMQ server is deleted
> using the ActiveMQ Administration web site.  Even though the message is gone
> on the server, the client continues to retry it.
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/NMS-1-5-client-not-recognizing-expired-messages-tp3357650p3357650.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Have you checked to see if your clock on the client machine is
synchronized with the Broker machine's clock?  Local Transactions hold
messages locally and redeliver them from local memory so if the clock
isn't sync'd then the client would redeliver the message when you roll
back the transaction regardless of the message being expired on the
broker.

Regards


-- 
Tim Bish
------------
FuseSource
Email: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/