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/11/28 18:43:00 UTC

[jira] [Updated] (CAMEL-18766) camel-support: background tasks without maxDuration are reeschedulable

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

Claus Ibsen updated CAMEL-18766:
--------------------------------
    Fix Version/s: 3.20.0

> camel-support: background tasks without maxDuration are reeschedulable
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-18766
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18766
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 3.18.3, 3.19.0
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Otavio Rodolfo Piske
>            Priority: Major
>             Fix For: 3.20.0
>
>
> This comes as a report from Michal Lück in a thread in Zulip chat: 
> ??"... I might have discovered an issue with the camel smpp component. It seems that if the producer never had a valid connection, it tries maxReconnect times to establish the connection but if those retries fail the BackgroundTask is looping and never returning. (similar behavior as in https://issues.apache.org/jira/browse/CAMEL-17472) ??
> ??I created a little example project to demonstrate my problem: [https://github.com/thuri/smpp-test"|https://github.com/thuri/smpp-test]??
> Subsequently explained as: 
> ??" ... I think the Problem is actually in the BackgroundTask class.??
> ??If the Budget for the task is created without maxDuration but with maxIterations, the scheduled task will never be canceled and run forever. It will only execute the actual delegate method (booleanSupplier) exactly maxIteration times but the task is still rescheduled doing nothing but logging a warning that the Budget has been consumed completely ..." ??



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