Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <31455792.4711274970473066.JavaMail.jira@thor>
Date: Thu, 27 May 2010 10:27:53 -0400 (EDT)
From: "Qingyi Gu (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2752) Message is delivered to DLQ in store
 and forward mode if two brokers clock is not in sync
In-Reply-To: <18075659.3871274905491786.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59575#action_59575 ] 

Qingyi Gu commented on AMQ-2752:
--------------------------------

I did tried "timestampplugin",  but it didn't solve the problem in this case.   I think it is because the plugin is mainly for the leg between jms client and broker.    My case is the leg between two brokers.     Yeah, we are seeking OS level protocol to keep clocks in sync to resolve this issue.

> Message is delivered to DLQ in store and forward mode if two brokers clock is not in sync
> -----------------------------------------------------------------------------------------
>
>                 Key: AMQ-2752
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2752
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.1
>         Environment: Windows 2003 Server,  ActiveMQ 5.3.1,  Camel 2.2.0 and Jboss 4.2.2
>            Reporter: Qingyi Gu
>
> I have two ActiveMQ running on two separated machines.  They use duplex network connector between them.    I am using camel InOut Pattern to send message cross these two brokers.    The InOut request timeout is 20 seconds.    If these two broker machines' clock is NOT in sync, at least the destination broker clock is more than 20 seconds ahead of the sender broker's clock,   when the message gets on destination broker side,  it is being delivered to DLQ right away.    I am not sure if there is a way to avoid this problem.  Or it just works as designed.

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