[
https://issues.apache.org/activemq/browse/AMQ-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38605
]
Dain Sundstrom commented on AMQ-1165:
-------------------------------------
I think you forgot to commit the test case.
> 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
> Fix For: 4.1.1, 4.2.0
>
> 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.
