[
https://issues.apache.org/jira/browse/CAMEL-25561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-25561:
--------------------------------
Fix Version/s: 4.24.0
> camel-jbang-mcp - after a failed restart, camel_run starts the integration
> again under the name it had
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25561
> URL: https://issues.apache.org/jira/browse/CAMEL-25561
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> camel_control restart starts an integration again with its own command line.
> When that fails, the integration is stopped, and the answer says: 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 starts with the
> default name (from the first route file) instead of the name it had (--name),
> so tools and scripts that find it by its name no longer do.
> 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).
> Proposal: remember the name of an integration whose restart failed, per
> directory, and have camel_run use it when no name is given; the answer of the
> failed restart says so.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
