GitHub user rajinisivaram reopened a pull request: https://github.com/apache/kafka/pull/3530
KAFKA-5595: Ensure client connection ids are not reused too quickly When there are broker delays that cause a response to take longer than `connections.max.idle.ms`, connections may be closed by the broker (as well as by the client) before the response is processed. If the port is reused, broker may send the outstanding response to a new connection with the reused port. The new connection will end up with correlation id mismatch, requiring process restart. This is also a security exposure since clients receive response intended for the wrong connection. You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-5595 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/3530.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3530 ---- commit 99f3374b5c3b0cb5efcdfe4c553aac943297b016 Author: Rajini Sivaram <rajinisiva...@googlemail.com> Date: 2017-07-15T13:01:47Z KAFKA-5595: Ensure client connection ids are not reused too quickly ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---