[ 
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.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.x
>
>
> 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)

Reply via email to