[
https://issues.apache.org/jira/browse/CAMEL-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691174#comment-17691174
]
Zheng Feng commented on CAMEL-19065:
------------------------------------
This should work since converting *byte[]* to *String* has been added in
[IOConverter|https://github.com/apache/camel/blob/f955a62d128804b45791d4f7e40b58ead58c866b/core/camel-base/src/main/java/org/apache/camel/converter/IOConverter.java#L147-L150].
You need to use
{code}
.log("LRA id is \${headers.Long-Running-Action}")
{code}
to convert it to String explicitly. *log("LOG \${headers}")* does not convert
each header.
> Saga Long-Running-Action header propagation might be broken with Kafka
> Component
> --------------------------------------------------------------------------------
>
> Key: CAMEL-19065
> URL: https://issues.apache.org/jira/browse/CAMEL-19065
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka, camel-lra
> Affects Versions: 3.20.2
> Reporter: Jose A. Iñigo
> Assignee: Zheng Feng
> Priority: Major
>
> As reported in the camel.zulipchat.com #camel stream, it seems that camel
> saga async workflows using the Kafka component might be losing the
> correlation between the original LRA header value since the Kafka component
> doesn't automatically turn it back into a String.
> Given the following route:
> {code:java}
> from("direct:bookings")
> .saga()
> .propagation(MANDATORY)
> .log("LOG1 \${headers}")
> .to("kafka:booking-requests?brokers=localhost:9092")
> from("kafka:booking-responses?brokers=localhost:9092")
> .saga()
> .propagation(MANDATORY)
> .log("LOG2 \${headers}") {code}
> When printing the headers we can see the Long-Running-Action with a String
> value:
>
> {code:java}
> LOG1 ...,Long-Running-Action=90EA3C7D191D45E-0000000000000001, ... {code}
>
> This headers are serialized as bytes by the Kafka Producer and sent to a
> topic _booking-requests_ where a processing application reads them and writes
> them back to {_}booking-responses{_}.
> The problem shows up in the second log statement, where the
> Long-Running-Action header is not 90EA3C7D191D45E-0000000000000001 anymore:
>
> {code:java}
> LOG2 Long-Running-Action=[B@4d4b56e8 {code}
> The Camel Saga component isn't automatically reformating the header value
> into a String.
> As a workaround we can provide a KafkaHeaderDeserializer to reconstruct it as
> a String:
>
> {code:java}
>
> from("kafka:booking-responses?brokers=localhost:9092&headerDeserializer=#kafkaHeaderStringDeserializer")
> .saga()
> .propagation(MANDATORY)
> .log("LOG2 \${headers}") {code}
>
> Here's a sample project where you can check this behaviour:
> [https://github.com/codependent/booking-service]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
