Claus Ibsen created CAMEL-27149:
-----------------------------------

             Summary: camel-jbang - camel stop <pid> of the process that 
launched an integration fails with exit code 3, which breaks Citrus
                 Key: CAMEL-27149
                 URL: https://issues.apache.org/jira/browse/CAMEL-27149
             Project: Camel
          Issue Type: Bug
          Components: camel-jbang
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 4.24.0


Since the 4.24 changes to the process commands (CAMEL-26911, CAMEL-26929), 
camel stop <pid> fails with exit code 3 ("No running Camel integration 
matches") when the pid is that of the process that launched the integration, 
such as the JBang launcher of camel run, rather than of the Camel JVM itself. 
In 4.23 a numeric pid was used as given, and the launcher got a SIGTERM.

This breaks Citrus, and so the integration tests of camel-kamelets on 
4.24.0-SNAPSHOT (apache/camel-kamelets#3186). Citrus 
(CamelStopIntegrationAction) keeps the pid of the process it started (the 
launcher, such as 3469), while the Camel JVM is its child (3470). At the end of 
each test it runs camel stop 3469, and only stops the child processes after 
that command succeeds. With 4.24 the command exits 3, Citrus fails the test, 
and the integration is never stopped: in CI the JVMs piled up until the runner 
was shut down.

Fix: when the pid given to camel stop is not a Camel integration, stop the 
running Camel integrations that are descendants of that process. A process that 
is not a Camel integration is still never signalled, as CAMEL-26911 requires, 
and a pid with no integration below it still fails with exit code 3.

_Claude Code on behalf of Claus Ibsen_




--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to