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

Pasquale Congiusti commented on CAMEL-19367:
--------------------------------------------

Thanks [~davsclaus], yeah, considering the following example:
{code}
BA60304B47DB867-0000000000000000 exchange created
BA60304B47DB867-0000000000000001 exchange created
BA60304B47DB867-0000000000000001 exchange sending to: mock://result
BA60304B47DB867-0000000000000001 exchange completed took: 760ms
BA60304B47DB867-0000000000000002 exchange created
BA60304B47DB867-0000000000000002 exchange sending to: mock://result
BA60304B47DB867-0000000000000002 exchange completed took: 762ms
BA60304B47DB867-0000000000000003 exchange created
BA60304B47DB867-0000000000000003 exchange sending to: mock://result
BA60304B47DB867-0000000000000003 exchange completed took: 762ms
BA60304B47DB867-0000000000000000 exchange completed took: 763ms
{code}
I guess I can just watch for the `BA60304B47DB867-0000000000000000 exchange 
completed took: 763ms` that is when the root step is completed (which is 
exactly what I need to know). It sounds fine and I'm going to test it soon to 
prove it solves the original issue.

Thanks for the suggestion,
Pasquale.

> CamelEvent.RouteCompleted
> -------------------------
>
>                 Key: CAMEL-19367
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19367
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 3.20.4
>            Reporter: Pasquale Congiusti
>            Priority: Major
>
> Hello team. While troubleshooting this Camel K issue [1], I've realized we're 
> missing some route event that can tell us that the route was completed. Do 
> you think it would be possible to include the `RouteCompleted` event? From 
> what I can tell, it would be an event generated once all the steps of the 
> route are completed. Without that, we don't know exactly when a route is 
> terminated and it's fine to gracefully stop it.
> Any feedback or possible workaround is appreciated as well, thanks!
> [1] https://github.com/apache/camel-k/issues/4343



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

Reply via email to