Croway opened a new pull request, #28245: URL: https://github.com/apache/camel/pull/28245
[CAMEL-25929](https://issues.apache.org/jira/browse/CAMEL-25929) Takes over #26871 by @TimurRakhmatullin86, who did not get back to the review. The first commit is theirs, cherry-picked unchanged except for the JIRA key in the subject. The second commit applies the changes requested on #26871. Restores the thread interrupt flag where an `InterruptedException` was swallowed: - `camel-core-processor`: `ConcurrentRequestsThrottler` restores the flag before `handleInterrupt()`, like `TotalRequestsThrottler` already does - `camel-aws2-kinesis`: `KclKinesis2Consumer.doStop()`, waiting for the graceful shutdown - `camel-cli-debug`: `CamelCliDebuggerFactory`, before returning - `camel-tahu`: `TahuEdgeClient.shutdown()` gives `InterruptedException` its own catch, so an `ExecutionException` or `CancellationException` does not flag the shutdown thread as interrupted - `camel-jbang-plugin-kubernetes`: `KubernetesPodLogs.sleepWell()` now returns `false` when interrupted and the retry loop stops. Before, every later `Thread.sleep` threw at once and the loop retried with no backoff. `camel-smpp` is left as it is. Restoring the flag there and then running the route on the interrupted jsmpp thread would make interruptible I/O in the route fail. Tested: built the 6 touched modules, ran the throttler tests in `camel-core` (67 tests) and the pod logs tests in `camel-jbang-plugin-kubernetes`. All passed. _Claude Code on behalf of @Croway_ -- 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]
