[
https://issues.apache.org/jira/browse/QPID-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049065#comment-14049065
]
ASF subversion and git services commented on QPID-5865:
-------------------------------------------------------
Commit 1607140 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1607140 ]
QPID-5865: Be more robust in face of system clock being changed:
- Separate Wall clock time uses from other time
* (assumed that any time with respect to the epoch is wallclock)
- For Posix use CLOCK_MONOTONIC for all non wall clock purposes
so that changing system time doesn't affect internal timekeeping
- For Windows kept the same time keeping scheme.
> The client and broker heartbeat code can get confiused when the system time
> changes
> -----------------------------------------------------------------------------------
>
> Key: QPID-5865
> URL: https://issues.apache.org/jira/browse/QPID-5865
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
>
> The underlying timekeeping code in C++ qpid currently uses CLOCK_REALTIME
> which is related to wallclock time and can go backwards and skip time
> forwards (either due to NTP or administrator action).
> This is not ideal because it can cause false timeouts to occur based on the
> system time rather than elapsed time.
> It would be better for most timing to be based on CLOCK_MONOTONIC which is
> steadily increasing time based on the system uptime. That will avoid problems
> due to the system time changing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
