[IGNITE-18826] Java thin client hangs on close

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.15
• Labels: ise
• Release Note: Java thin client: fixed the pending requests race on close
• Ignite Flags: Release Notes Required
• Assignee: Nikita Amelchev
• Reporter: Nikita Amelchev
• Created: 16/Feb/23 14:26
• Updated: 21/Feb/23 12:25
• Resolved: 20/Feb/23 10:51

Description

There are several places where thin client threads can hang:

GridNioClientConnectionMultiplexer: SSL enabled + PA enabled

// Can return finished future with error -> sslHandshakeFut will not complete.
GridNioFuture<GridNioSession> sesFut = srv.createSession(ch, meta, false, null);

 if (sslHandshakeFut != null)
      sslHandshakeFut.get();

TcpClientChannel: PA enabled

ClientRequestFuture fut = new ClientRequestFuture(requestId, ClientOperation.HANDSHAKE);

 // TcpClientChannel may be closed and fut will not complete.
assert !closed.get();

pendingReqs.put(requestId, fut);
...
ByteBuffer buf = timeout > 0 ? fut.get(timeout) : fut.get();

Issue Links

• relates to: IGNITE-14789 Thin client startup hangs if an error occur during SSL handshake
• relates to: IGNITE-18591 Java thin client: Cluster discovery
• links to: GitHub Pull Request #10549