You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2024/01/04 08:46:00 UTC

[jira] [Updated] (CAMEL-20225) camel-core: modernize management of duration and timestamps

     [ https://issues.apache.org/jira/browse/CAMEL-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Otavio Rodolfo Piske updated CAMEL-20225:
-----------------------------------------
    Fix Version/s: 4.4.0
                       (was: 4.x)

> camel-core: modernize management of duration and timestamps 
> ------------------------------------------------------------
>
>                 Key: CAMEL-20225
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20225
>             Project: Camel
>          Issue Type: Task
>          Components: camel-core
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Otavio Rodolfo Piske
>            Priority: Major
>             Fix For: 4.4.0
>
>
> We have many places in the code where do perform logic that mixes operations between monotonic and real time clocks. 
> For instance, we have instances with code like this: 
> {code:java}
> long elapsed = System.currentTimeMillis() - exchange.getCreated();
> {code}
> The problem with this code is that it can provide incorrect data in some circumstances, because it computes the duration from a real time clock (which, for instance, can go back in time in some cases). 
> We need to rework this to create interfaces for computing both duration as well as pointing the specific point in time in which it was created.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)