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

Work on CAMEL-26949 started by shashank.
----------------------------------------
> camel-test-dst - let a world move the wall clock apart from the monotonic 
> clock
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-26949
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26949
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-test
>            Reporter: shashank
>            Assignee: shashank
>            Priority: Minor
>
> In camel-test-dst the wall clock is derived from the virtual monotonic time 
> (a fixed epoch plus the virtual time), so it can never jump. Real wall clocks 
> do: NTP corrections, a VM resumed after a pause, a container moved between 
> hosts. Code that reads the wall clock then sees time move backward or leap 
> forward while the monotonic clock goes on normally.
> Camel code that uses wall-clock time and has had timing bugs:
> * expiring idempotent and key-value repositories and caches (CAMEL-26737, 
> CAMEL-26740);
> * timer, scheduler and cron/quartz schedules (CAMEL-25848).
> h3. Proposal
> A world API to move the wall clock forward or backward by a given amount at a 
> chosen step, without touching the monotonic clock, through the internal 
> {{TimeSource}} of CAMEL-25911. The seed decides when the jump happens and how 
> big it is, so a failing run replays exactly. Document it in the guide with 
> one example (an expiring repository under a backward jump).
> This is harness-only; worlds that use it come later, under CAMEL-26610.
> _Filed with Claude Code on behalf of allthingssecurity._



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to