[
https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kerry Bonin updated QPID-1904:
------------------------------
Attachment: qpid-1904.patch
The underlying problem appears to be as described - boost::posix::ptime
inherits its epoch from the underlying platform, causing a discrepancy across
some platforms. This is primarily an issue for Windows.
The applied patch adds a static variable to the Duration class equal to the
qpid specified epoch in TimePrivate format, which is a boost::posix::ptime
value, and initialized using the boost::Gregorian::date class. This is used in
the Duration constructor taking an AbsTime value in place of
ptime(min_date_time). The comments in Time.h are updated to reflect the epoch
correction.
> Timestamps are incorrect
> ------------------------
>
> Key: QPID-1904
> URL: https://issues.apache.org/jira/browse/QPID-1904
> Project: Qpid
> Issue Type: Bug
> Components: Qpid Managment Framework
> Affects Versions: 0.5
> Environment: Windows XP
> Reproduced both with the python API and the .Net API
> Reporter: Julien Lavigne du Cadet
> Attachments: qpid-1904.patch, qpid-dates.png
>
>
> The timestamps for configuration and instrumentation messages are incorrect
> both with the python and the .Net api.
> According to the documentation "All timestamps are uint64 values representing
> nanoseconds since the epoch (January 1, 1970)." However, the dates resulting
> can be several years in the past or in the future.
> To reproduce with the python api :
> - in disp.py, line 178 add the following line :
> print gmtime (nsec / 1000000000)
> - start qpid-tool and list the queues => the full dates will be displayed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
