[jira] [Commented] (CAMEL-24706) camel-main - camel.main.duration alias of durationMaxSeconds with a time unit (15s, 2m)

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-24706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114839#comment-18114839 ] 

Claus Ibsen commented on CAMEL-24706:
-------------------------------------

Merged to main in PR https://github.com/apache/camel/pull/26364.

> camel-main - camel.main.duration alias of durationMaxSeconds with a time unit (15s, 2m)
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24706
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24706
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-main
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.23.0
>
>
> Add camel.main.duration as an alias of camel.main.durationMaxSeconds that accepts a value with a time unit (15s, 2m, 1h, or a plain number of seconds).
> Why: while benchmarking AI-assisted route authoring (camel-jbang-mcp, local and hosted models, 14 runs on 2026-09-13), the model wrote camel.main.duration=15s (or duration-seconds, durationSeconds) in application.properties in nearly every run, and lost a correction round each time to "Unknown option". A human rarely sets this option, but an AI uses it during development to make a run stop by itself, so the natural spelling should work. The CLI already has --max-seconds.
> Suggested: a String option duration on MainConfigurationProperties (camel-main) that parses the value with TimeUtils.toMilliSeconds and sets durationMaxSeconds; documented in the main configuration metadata so the catalog validators and the camel-jbang-mcp tools accept it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)