Thanks Omar. I was looking at ProducerRecord because I was thinking about
trying to use Spring Kafka.
I am not sure yet, but part of the issue is that in the camel code, what is
being called the paritionKey is not. It is the partition (number). The docs
do the same thing. The partitionKey is a
Weird, from experience, I have seen this timeout happen if the specified
partition doesn't exist.
However, since you are using Camel 3.9 and you didn't set a message key,
the partition key won't be set in the ProducerRecord, it will be only set
if you set the message key, however this behavior
Setting the message key does not help. :(
On Mon, Apr 19, 2021 at 11:20 AM Mark Nuttall wrote:
> I've never set the message key. I might give that a shot.
>
> The route is pretty simple. And the only headers being set are the
> partition key and another string value i need to be passed. The
I've never set the message key. I might give that a shot.
The route is pretty simple. And the only headers being set are the
partition key and another string value i need to be passed. The body is
JSON.
I am running Kafka locally (so whatever partitions is the default) and AWS
MSK - 2
Hi
Yes use camel-spring-boot-bom as its Spring Boot that fuckup when
there are class dependencies problems.
So its better to use what Spring Boot provides out of the box.
And we will upgrade reactor-core for Camel 3.10
On Mon, Apr 19, 2021 at 1:39 PM Delgado, Michael
wrote:
>
> Hi everyone,
>
Hi everyone,
I had a problem in my spring boot application when updating from camel 3.8.0 to
3.9.0. My WebClient calls which uses .block(Duration) method (belonging to
reactor-core artifact) do not work anymore.
Versioning:
Java 11.0.2.
Spring boot 2.4.4.
Camel 3.9.0.
My pom:
...
Hi Mark,
When you send your message to Kafka, do you as well set the message key or
you just set the partition key? Perhaps it would be great if you can post
an example for your route with the headers/body that you set, that could
help us here to troubleshoot the issue. Also, how many partitions
