activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1165) RegionBroker resets JMS Timestamp
Date Sun, 25 Feb 2007 08:32:03 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38573
] 

Hiram Chirino commented on AMQ-1165:
------------------------------------

That logic was put in place as a "Feature"..  In rev 511463 in 4.1 trunk I have now made that
"Feature" optional so that we don't break JMS compliance.

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


Mime
View raw message