[
https://issues.apache.org/jira/browse/CAMEL-21792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21792:
--------------------------------
Fix Version/s: 4.10.1
(was: 4.10.2)
> camel-aws - KCL Kinesis Consumer fails with NPE when using custom async client
> ------------------------------------------------------------------------------
>
> Key: CAMEL-21792
> URL: https://issues.apache.org/jira/browse/CAMEL-21792
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2-kinesis
> Affects Versions: 4.10.0
> Environment: Using localstack on MacOS, version 4.10.0.
> Reporter: Mark Wimpory
> Assignee: Andrea Cosentino
> Priority: Minor
> Fix For: 4.10.1, 4.11.0
>
> Attachments: WranglerKinesisKCLRouteBuilder.java,
> image-2025-02-25-12-01-26-827.png, image-2025-02-25-12-03-17-781.png,
> image-2025-02-25-12-03-49-037.png
>
>
> The camel kinesis consumer fails when KCL is set to true.
> !image-2025-02-25-12-03-17-781.png!
>
> !image-2025-02-25-12-03-49-037.png!
>
> I have isolated the issue to the below. The kinesis client exists in the
> configuration according to debug but the consumer is reading from the
> endpoint:
> !image-2025-02-25-12-01-26-827.png|width=781,height=249!
> The other clients (dynamodb and cloudwatch) are created withing if statements
> and include a reference to the configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)