Claus Ibsen created CAMEL-24860:
-----------------------------------
Summary: camel-core - a failed route reload in dev mode leaves the
previous route stopped: keep it running, or say that nothing runs
Key: CAMEL-24860
URL: https://issues.apache.org/jira/browse/CAMEL-24860
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Found by the stepwise half of the round-2 local-model benchmark (ten
camel-jbang-examples built step by step through the camel-jbang-mcp server,
five runs each, 2026-09-21).
When a route file is saved with a mistake the loader rejects, the file watcher
reload strategy stops and removes the previous route first, then fails to load
the new one, and logs "Error reloading routes from file ... This exception is
ignored." The app then runs with no route at all until the next successful
save: in the series a cron route was gone for 22 seconds after a bad save, and
the log showed only "Pausing trigger / Deleting job".
Options: load and validate the new routes before stopping the old ones, and
keep the old ones when the new fail (the safest edit-run loop); or, if that is
not feasible for every case, log at WARN that the previous route was stopped
and nothing runs for that file until it is fixed. The first is what a developer
expects from live reload.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
