Croway opened a new pull request, #27382: URL: https://github.com/apache/camel/pull/27382
## Summary Backport of #27214 ([CAMEL-25197](https://issues.apache.org/jira/browse/CAMEL-25197)) to `camel-4.18.x` (already on `main` and, via #27215, on `camel-4.22.x`). `LocalCliConnector.sigterm()` runs the termination on a single-thread executor that is never shut down: its non-daemon `Terminate JVM task` thread stays parked once Camel is stopped. On 4.18.x `Main.main` does not call `System.exit` after a normal shutdown (CAMEL-23230 is not on this branch), so a plain Camel Main application never exits after `camel stop` or after its `~/.camel/{pid}` lock file is deleted. Verified end to end with a Camel Main 4.18.4 app (timer route + camel-cli-connector), deleting the lock file: | Connector | Result | |---|---| | 4.18.4 released | Camel shuts down, JVM still alive after 30 s (`Camel Thread #4 - Terminate JVM task` parked) | | this branch | JVM exits ~1 s after the delete | ## Not a straight cherry-pick The code change is identical to #27214. The test needed adapting, because `camel-cli-connector` has no tests on this branch: - `camel-test-junit5` instead of `camel-test-junit6` - `assertj-core` and `awaitility` test dependencies added to the module's `pom.xml` `LocalCliConnectorSigtermTest` passes with the fix and fails without it (20 s timeout). _Claude Code on behalf of Croway_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
