You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/05/27 10:30:52 UTC

[jira] Commented: (AMQ-2752) Message is delivered to DLQ in store and forward mode if two brokers clock is not in sync

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

Gary Tully commented on AMQ-2752:
---------------------------------

it is working as designed. 
The feature that helps work around this issue is http://activemq.apache.org/timestampplugin.html but if possible, use some OS level protocol to keep the system clocks in sync on each of the machines.

> 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.