You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikita Amelchev (Jira)" <ji...@apache.org> on 2023/02/16 14:32:00 UTC
[jira] [Updated] (IGNITE-18826) Java thin client hungs on close
[ https://issues.apache.org/jira/browse/IGNITE-18826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikita Amelchev updated IGNITE-18826:
-------------------------------------
Labels: ise (was: )
> Java thin client hungs on close
> -------------------------------
>
> Key: IGNITE-18826
> URL: https://issues.apache.org/jira/browse/IGNITE-18826
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Major
> Labels: ise
> Fix For: 2.15
>
>
> There are several places where thin client threads can hang:
> GridNioClientConnectionMultiplexer: SSL enabled + PA enabled
> {noformat}
> // Can return finished future with error -> sslHandshakeFut will not complete.
> GridNioFuture<GridNioSession> sesFut = srv.createSession(ch, meta, false, null);
> if (sslHandshakeFut != null)
> sslHandshakeFut.get();
> {noformat}
> TcpClientChannel: PA enabled
> {noformat}
> 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();
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)