[IGNITE-20759] Tcp handshake in communication spi hangs on JDK 12 and later

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.15
• Fix Version/s: 2.16
• Labels: ise
• Release Note: Fixed writing post-handshake message in NIO server
• Ignite Flags: Release Notes Required
• Assignee: Ivan Daschinsky
• Reporter: Ivan Daschinsky
• Created: 30/Oct/23 07:12
• Updated: 20/Nov/23 19:39
• Resolved: 17/Nov/23 11:49

Description

This issue is reproduced in GridTcpCommunicationSpiSslSelfTest. All tests hangs during tcp handshake process in infinite loop in org.apache.ignite.spi.communication.tcp.internal.TcpHandshakeExecutor#tcpHandshake. Seems that fixes in IGNITE-16622 are not enough

The main reason of this behaviour – https://bugs.openjdk.org/browse/JDK-8277307. Post handshake message seems to be too large for being written in one step, but we don't try to resend the rest in org.apache.ignite.internal.util.nio.GridNioServer.DirectNioClientWorker#processWriteSsl since the ssl handshake is considered to be finished.

WA – set -Djdk.tls.server.enableSessionTicketExtension=false

Issue Links

• relates to: IGNITE-16622 Add support for JDK 17
• links to: GitHub Pull Request #11036
• links to: Run SPI suite on JDK 11 and 17