You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/02/25 09:30:02 UTC
[jira] Assigned: (AMQ-1165) RegionBroker resets JMS Timestamp
[ https://issues.apache.org/activemq/browse/AMQ-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino reassigned AMQ-1165:
----------------------------------
Assignee: Hiram Chirino
> RegionBroker resets JMS Timestamp
> ---------------------------------
>
> Key: AMQ-1165
> URL: https://issues.apache.org/activemq/browse/AMQ-1165
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.0
> Reporter: Dain Sundstrom
> Assigned To: Hiram Chirino
> Attachments: Timestamp.patch
>
>
> The RegionBroker contains the following logic, which overwrites the JMSTimestamp. FWIU, the message timestamp should be set once at send and never changed by the broker.
> if (message.getTimestamp() > 0 && (message.getBrokerPath() == null || message.getBrokerPath().length == 0)) {
> //timestamp not been disabled and has not passed through a network
> message.setTimestamp(System.currentTimeMillis());
> }
> Attached is a simple test case and patch that changes the '>' in the if statement above to '<='. I'm not sure if that is the proper fix, but it did make my problem go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.