davsclaus opened a new pull request, #27700: URL: https://github.com/apache/camel/pull/27700
Jira: https://issues.apache.org/jira/browse/CAMEL-25561 `camel_control restart` starts an integration again with its own command line. When that fails, the integration is stopped and the answer said: "fix the cause below, then camel_run starts it again". An agent that follows this calls `camel_run` with the directory only, and the integration started under the default name (from the first route file) instead of its own (`--name`), so the tools and scripts that find it by its name no longer did. Found in the local-model benchmark: an integration started as `run-order-generator` came back as `order-generator` after a failed restart, and every later check by name failed (3 of 13 runs). Now: - the name of an integration whose restart failed is kept by its directory (its real path); - `camel_run` without a name uses it, and its answer says "Started run-order-generator (pid N), under the name it had before its restart failed"; once started, the name is forgotten; - the answer of the failed restart names it: "... then camel_run starts it again (directory /path) under the same name, run-order-generator." A name given to `camel_run` is used as before. Tests: `IntegrationLauncherTest.camelRunKeepsTheNameOfAnIntegrationWhoseRestartFailed`; the `IntegrationLauncher*Test` classes pass (11 tests). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- 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]
