[
https://issues.apache.org/jira/browse/CAMEL-25818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25818.
---------------------------------
Resolution: Fixed
> camel-jbang-mcp - the console output of camel_run and camel_control restart
> stays in ~/.camel until the server exits
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25818
> URL: https://issues.apache.org/jira/browse/CAMEL-25818
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> {{camel_run}} and {{camel_control restart}} send the console output of the
> process they start to {{~/.camel/camel-launch-<number>.log}} and
> {{~/.camel/camel-restart-<number>.log}}. They read the file only to answer:
> the cause and the output of a start that failed, or the output of a run that
> is still starting. The file is deleted only when the server JVM exits
> ({{deleteOnExit}}). So each start leaves one file, and the file keeps growing
> while the integration runs and logs.
> On a machine that ran the AI benchmark this morning there were 8 such files,
> 12.4 MB together. The largest was 11 MB. A server that runs for days keeps
> one file per start.
> Two options:
> * Delete the file when the process ends (the launcher can watch it with
> {{Process.onExit()}}).
> * Keep the console output of the last process of each integration, next to
> the log of its previous run (CAMEL-25784). The console output can have what
> the log does not, such as what the code prints to stdout, or the error of a
> JVM that crashed.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
