Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 71690 invoked from network); 19 Oct 2009 14:24:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Oct 2009 14:24:51 -0000 Received: (qmail 25342 invoked by uid 500); 19 Oct 2009 14:24:50 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 25273 invoked by uid 500); 19 Oct 2009 14:24:50 -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 25263 invoked by uid 99); 19 Oct 2009 14:24:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2009 14:24:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2009 14:24:41 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Mzt9o-0003d4-0P for users@activemq.apache.org; Mon, 19 Oct 2009 07:24:20 -0700 Message-ID: <25959214.post@talk.nabble.com> Date: Mon, 19 Oct 2009 07:24:20 -0700 (PDT) From: MrBunt1 To: users@activemq.apache.org Subject: Re: ActiveMQ 5.2 messages with Time to Live sent straight to DLQ In-Reply-To: <25874614.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jonathan.dodd@nhsbt.nhs.uk References: <25874614.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org I have now solved this problem. It was a timing issue. The "errant" spoke did not have the "Automatically adjust clock for daylight saving changes" ticked, whereas the other machines on my network of brokers did. Although all three clocks displayed the same time, two were using BST and one was using GMT - and ActiveMQ was treating the server using GMT as one hour behind, which kind of makes sense now. -- View this message in context: http://www.nabble.com/ActiveMQ-5.2-messages-with-Time-to-Live-sent-straight-to-DLQ-tp25874614p25959214.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.