Robbie Gemmell created PROTON-1583:
--------------------------------------
Summary: handle edge cases when driving transport#tick(now) with
nanoTime derived values
Key: PROTON-1583
URL: https://issues.apache.org/jira/browse/PROTON-1583
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Affects Versions: proton-j-0.21.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Fix For: proton-j-0.22.0
Transport#tick is driven with time values representing 'now' in milliseconds.
This is often done with System.currentTimeMillis(), however that varies with
the wall clock so there are advantages to deriving the value from
System.nanoTime() which does not. There are some edge cases the existing tick
implementation doesn't handle when doing that (such as values wrapping and a
possible clash of actual deadline zero with use of zero as a
not-initialized/no-idle-timeout indicator) which could lead to incorrect
behaviour and needs addressed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
