[
https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859970#action_12859970
]
Andrew Stitcher commented on QPID-1904:
---------------------------------------
Since r931782 There has been an explicit constant AbsTime for the Epoch. Every
place that used to just convert an AbsTime into a Duration -
Duration(AbsTime::now()) (which was always an operation with dubious semantics)
should now do - Duration(AbsTime::EPOCH, AbsTime::now()).
And the Duration constructor taking an AbsTime should be removed.
> 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
> Assignee: Andrew Stitcher
> 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:dev-subscr...@qpid.apache.org
