[jira] [Updated] (CAMEL-24271) camel-kafka - Use BackgroundTask for reconnection so it is visible in internal tasks

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen updated CAMEL-24271:
--------------------------------
    Fix Version/s: 4.22.0

> camel-kafka - Use BackgroundTask for reconnection so it is visible in internal tasks
> ------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24271
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24271
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>              Labels: help-wanted
>             Fix For: 4.22.0
>
>
> Currently camel-kafka uses ForegroundTask for the create/subscribe steps during reconnection (KafkaFetchRecords). The overall reconnection loop runs in its own thread with a do/while loop, so the retry state is not visible via the internal-tasks dev console or TUI.
> Other components like camel-sjms and camel-pgevent use BackgroundTask which registers with the TaskManagerRegistry during the entire retry period, making reconnection attempts visible to operators via:
> - camel get internal-task (CLI)
> - Internal Tasks tab in the TUI
> - JMX ManagedTaskManagerRegistry
> Switching camel-kafka to use BackgroundTask for its reconnection loop would let users observe retry progress, attempt count, delay, elapsed time, and errors when a Kafka broker goes down.



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