[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Resolved: (AMQ-2752) Message is delivered to DLQ in store
From:       "Gary Tully (JIRA)" <jira () apache ! org>
Date:       2010-05-27 15:24:53
Message-ID: 30275406.4871274973893216.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Gary Tully resolved AMQ-2752.
-----------------------------

    Fix Version/s: 5.4.0
       Resolution: Fixed

in r948858, added processNetworkMessages attribute (default false) to \
TimeStampBrokerPlugin to allow it to modify network messages. 

> 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
> Assignee: Gary Tully
> Fix For: 5.4.0
> 
> 
> 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.


[prev in list] [next in list] [prev in thread] [next in thread]