activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@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
Date Thu, 27 May 2010 15:06:53 GMT

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

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

ah, you may need to provide your own variant of the timestamp broker plugin, it is quite simple.
Currently, it does not work if a message has come from a network which is your use case. not
sure why that is, I think that should be made optional. In the code it has{code}if (message.getTimestamp()
> 0
            && (message.getBrokerPath() == null || message.getBrokerPath().length
== 0)) {
            // timestamp not been disabled and has not passed through a network{code}. which
ensures it does not work for your use case atm.

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


Mime
View raw message