gnodet opened a new pull request, #23770: URL: https://github.com/apache/camel/pull/23770
[CAMEL-23686](https://issues.apache.org/jira/browse/CAMEL-23686) ## Summary - Fix `createCopy()` and `createCorrelatedCopy()` resetting the **original** exchange's clock instead of the **copy's** clock ## Problem In `PooledProcessorExchangeFactory`, both `createCopy()` (line 76) and `createCorrelatedCopy()` (line 100) called: ```java ((ResetableClock) exchange.getClock()).reset(); // resets ORIGINAL ``` This should be: ```java ((ResetableClock) answer.getClock()).reset(); // resets COPY ``` The `create()` method (line 130) was already correct. The bug meant copy exchanges carried stale timestamps from the pool while the original exchange's clock was incorrectly reset mid-processing. ## Test plan - [x] Existing unit tests pass - [x] Verified `create()` method already uses correct pattern -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
