From dev-return-21964-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Mon Sep 06 08:31:28 2010 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 99038 invoked from network); 6 Sep 2010 08:31:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Sep 2010 08:31:28 -0000 Received: (qmail 53858 invoked by uid 500); 6 Sep 2010 08:31:28 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 53654 invoked by uid 500); 6 Sep 2010 08:31:24 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 53640 invoked by uid 99); 6 Sep 2010 08:31:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Sep 2010 08:31:23 +0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.216.178 as permitted sender) Received: from [209.85.216.178] (HELO mail-qy0-f178.google.com) (209.85.216.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Sep 2010 08:31:18 +0000 Received: by qyk36 with SMTP id 36so5637153qyk.2 for ; Mon, 06 Sep 2010 01:30:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=6eG/TJ7OasF2V2gFSV/IGiySZ0CJ8WfADCYkDtwpC0U=; b=Fdwaq1tlFcTPWNMULpyTogzsu2ZFwFeKdBRasDExQwkrjKCvvXGpHDnmVL+xv/MrCH ggbHCCIo2xt9mnNN6wXbPloDXk183i6iRzBrj5LBxj7JkVmkvTZ0Ph0oXclt7lneziXT O61EBKuSEQDl9PVNOXrALgXDO1VvPeggUOSWw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ruLgln++TEzjvCVRfCFPncWMg5G99jEXILL2icMtQXdq/gmJD8rX/3OOkhgyNJQfTA jqtdzdGAbOh7IlSxQv1e8yl9C53lQjKyp/tOWBGXjlKSrQxyaTsb50EC9vWBevRy4dhP SGX0hzRNb5ScehWe/MfjJklEIiEJ3msdF/wYk= MIME-Version: 1.0 Received: by 10.229.205.234 with SMTP id fr42mr2633229qcb.258.1283761857120; Mon, 06 Sep 2010 01:30:57 -0700 (PDT) Received: by 10.229.71.198 with HTTP; Mon, 6 Sep 2010 01:30:57 -0700 (PDT) In-Reply-To: <1283538944922-2526089.post@n4.nabble.com> References: <1283525299509-2525789.post@n4.nabble.com> <1283538944922-2526089.post@n4.nabble.com> Date: Mon, 6 Sep 2010 09:30:57 +0100 Message-ID: Subject: Re: ActiveMQ issue across multiple domains From: Gary Tully To: dev@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 There is also the time stamp broker plugin that can help in this scenario to update the message time stamps to match the brokers clock: see: http://activemq.apache.org/timestampplugin.html On 3 September 2010 19:35, vivekmshukla wrote: > > I was able to figure out this issue. I just wanted to share my resolution in > case somebody faces similar situation in future. > > The issue was not related to domain or machine plateform at all. The issue > was due to the time difference in the system clocks on the domains where I > had my publisher and broker. The clock on the broker machine was ahead of > the publisher machine clock. So by the time the topic message was reaching > on the broker, it was already expired and my subscriber never picked the > messages. It worked perfectly fine where clocks on the machines were in > sync. In order to fix the issue, I ensured that machine clocks were in sync. > -- > View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-issue-across-multiple-domains-tp2525789p2526089.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > -- http://blog.garytully.com Open Source Integration http://fusesource.com