You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Cliff Jansen (JIRA)" <ji...@apache.org> on 2018/12/10 20:32:00 UTC
[jira] [Commented] (PROTON-1981) Wrong posix time for
pn_proactor_now()
[ https://issues.apache.org/jira/browse/PROTON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715515#comment-16715515 ]
Cliff Jansen commented on PROTON-1981:
--------------------------------------
Looking at the doc for pn_proactor_now() in proactor.h, the 32 bit value returned is not intended for use in a timestamp on its own. So perhaps the fault lies exclusively in the implementation of timestamp::now().
> Wrong posix time for pn_proactor_now()
> --------------------------------------
>
> Key: PROTON-1981
> URL: https://issues.apache.org/jira/browse/PROTON-1981
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
> Affects Versions: proton-c-0.26.0
> Reporter: Cliff Jansen
> Assignee: Cliff Jansen
> Priority: Major
>
> Uses MONOTONIC instead of REALTIME, hence not anchored to UNIX epoch as per AMQP standard.
>
> Used by proton::timestamp::now()
>
> Can take you back to 1970 on Centos7. Other time travel destinations possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org