You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Qingyi Gu (JIRA)" <ji...@apache.org> on 2010/05/26 22:24:51 UTC
[jira] Created: (AMQ-2752) Message is delivered to DLQ in store and
forward mode if two brokers clock is not in sync
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.
[jira] Commented: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Qingyi Gu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Qingyi Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59582#action_59582 ]
Qingyi Gu commented on AMQ-2752:
--------------------------------
Tested with r948858, it works now. Thanks.
> 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.
[jira] Commented: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully reassigned AMQ-2752:
-------------------------------
Assignee: Gary Tully
> 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
>
> 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.
[jira] Commented: (AMQ-2752) Message is delivered to DLQ in store
and forward mode if two brokers clock is not in sync
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ 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.