You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/01/09 08:40:00 UTC

[jira] [Updated] (CAMEL-17427) Option to restore old behaviour of scheduled consumers healthcheck

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

Claus Ibsen updated CAMEL-17427:
--------------------------------
    Fix Version/s: 3.15.0

> Option to restore old behaviour of scheduled consumers healthcheck
> ------------------------------------------------------------------
>
>                 Key: CAMEL-17427
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17427
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 3.13.0, 3.14.0
>            Reporter: MichaƂ Ostrowski
>            Priority: Major
>             Fix For: 3.15.0
>
>
> In version 3.13.0 behaviour of scheduled consumers helath checks was changed. Consumer is considered DOWN until at least one successful execution - CAMEL-17168.
> In case of rarely executed routes (i.e. once a day), consumer could be DOWN for several hours. It causes Camel context to be DOWN and in our case whole Spring Boot application to be DOWN.
> Our workaround is to disable consumers healthchecks, but it's a shame to give up on this nice feature.
> Possible solution would be to add configuration option to enable old health logic for specific consumers, or at least on whole context.
> I'm willing to provide patch but I want to discuss optimal solution.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)