The MySqlStreamingChangeEventSource will call the client.disconnect() during the source's finally block and randomly blocks when there is a deadlock between the main thread and the keep-alive thread. This has been reported upstream in https://github.com/osheroff/mysql-binlog-connector-java/issues/133.

The issue is we don't know what triggers the shutdown to safely reproduce the scenario and so I recommend we add some extra logging at the INFO level to capture the exception stack trace early as a way to determine why this happens so in the case of a deadlock, the logs can at least be helpful.