[
https://issues.apache.org/jira/browse/KAFKA-9854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261219#comment-17261219
]
Alexandru Ionescu commented on KAFKA-9854:
------------------------------------------
The latest Strimzi Operator creates brokers using the 2.6.0 version of Kafka.
For the clients we have Spring Boot applications that have Spring Kafka 2.5.4
that include kafka-clients 2.5.0.
I am doing now tests with an overriden version using Spring Kafka 2.6 and
kafka-clients 2.5.1 which should have your fix.
Regards,
Alex
> Re-authenticating causes mismatched parse of response
> -----------------------------------------------------
>
> Key: KAFKA-9854
> URL: https://issues.apache.org/jira/browse/KAFKA-9854
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Critical
> Fix For: 2.6.0, 2.5.1
>
>
> the schema of LIST_OFFSETS consists of
> # throttle_time_ms:INT32 and
> # responses:ARRAY
>
> If throttle_time_ms is zero and size of responses is small enough, its
> binary is compatible to schema of SASL_HANDSHAKE composed of
> # error_code:INT16 and
> # mechanisms:ARRAY(STRING)
>
> Hence, there is no Schema error when SASL_HANDSHAKE tries to parse response
> of LIST_OFFSETS but the check of correction id throws IllegalStateException
> due to mismatched error. The IllegalStateException is NOT caught and the
> mismatched response is not sent back to Selector so the cascading error
> happens that all following responses are parsed by incorrect Schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
