[ 
https://issues.apache.org/jira/browse/KAFKA-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809996#comment-16809996
 ] 

Rajini Sivaram commented on KAFKA-8154:
---------------------------------------

[~rnataraja] [~gordonmessmer] From the buffer sizes that [~rnataraja] provided, 
read buffer size is {color:#000000}18437{color} and application buffer size is 
16384. This looks like the SSLEngine is using buffer sizes that don't match, 
i.e. application buffer size is too small to unwrap a single packet buffer. As 
mentioned earlier, the buffer sizes I looked at (Oracle JDK jdk1.8.0_191 and 
the Kafka system test docker image that uses OpenJDK 1.8.0_181) both have 
smaller packet buffer size and large application buffer size. The SSL 
implementation in Kafka currently does not support mismatched buffer sizes and 
that looks more like an issue with the SSLEngine. It will be good to know if 
the issue [~gordonmessmer] ran into was with the same buffer sizes and the same 
SSL provider.

I looked at several JDKs and couldn't find one that uses buffer sizes that 
don't match. I couldn't find a download for the exact one that [~rnataraja] 
used. If one of you can write a test that recreates the scenario, that would be 
useful before implementing a fix. Otherwise if you do know of an easily 
downloadable JDK with the issue, I can help with writing the test. I would be 
nervous about merging a fix that cannot be tested.

 

 

> Buffer Overflow exceptions between brokers and with clients
> -----------------------------------------------------------
>
>                 Key: KAFKA-8154
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8154
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 2.1.0
>            Reporter: Rajesh Nataraja
>            Priority: Major
>         Attachments: server.properties.txt
>
>
> https://github.com/apache/kafka/pull/6495
> https://github.com/apache/kafka/pull/5785



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to