You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Tadayoshi Sato (Jira)" <ji...@apache.org> on 2024/07/08 08:28:00 UTC

[jira] [Updated] (CAMEL-20953) camel-jbang - --max-* options with --dev fails to terminate the Camel context

     [ https://issues.apache.org/jira/browse/CAMEL-20953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tadayoshi Sato updated CAMEL-20953:
-----------------------------------
    Description: 
When we'd like to run a Camel script once and then immediately self-terminate it, we'd run the command:
{code}
camel run hello.java --max-messages=1
{code}
and it works just as expected. However, when we add {{--dev}} to the above command, it starts to fail to terminate the context and thus the process.
{code}
camel run hello.java --max-messages=1 --dev
{code}

The same issue goes for {{\-\-max\-idle\-seconds}} and {{--max-seconds}} as well.

Normally it wouldn't be an issue, but it becomes an issue when we run a Camel script on VS Code, where the [Debug Adapter for Apache Camel|https://github.com/camel-tooling/camel-debug-adapter] always attaches {{--dev}} to the launcher command.

  was:
When we'd like to run a Camel script once and then immediately self-terminate it, we'd run the command:
{code}
camel run hello.java --max-messages=1
{code}
and it works just as expected. However, when we add {{--dev}} to the above command, it starts to fail to terminate the context and thus the process.
{code}
camel run hello.java --max-messages=1 --dev
{code}

The same issue goes for {{\-\-max\-idle\-seconds}} and {{--max-seconds}} as well.

Normally it wouldn't be an issue, but it becomes an issue when we run a Camel script on VS Code, where the [Debug Adapter for Apache Camel|https://github.com/camel-tooling/camel-debug-adapter] always attach {{--dev}} to the launcher command.


> camel-jbang - --max-* options with --dev fails to terminate the Camel context
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-20953
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20953
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>    Affects Versions: 4.7.0
>            Reporter: Tadayoshi Sato
>            Priority: Major
>
> When we'd like to run a Camel script once and then immediately self-terminate it, we'd run the command:
> {code}
> camel run hello.java --max-messages=1
> {code}
> and it works just as expected. However, when we add {{--dev}} to the above command, it starts to fail to terminate the context and thus the process.
> {code}
> camel run hello.java --max-messages=1 --dev
> {code}
> The same issue goes for {{\-\-max\-idle\-seconds}} and {{--max-seconds}} as well.
> Normally it wouldn't be an issue, but it becomes an issue when we run a Camel script on VS Code, where the [Debug Adapter for Apache Camel|https://github.com/camel-tooling/camel-debug-adapter] always attaches {{--dev}} to the launcher command.



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