[
https://issues.apache.org/jira/browse/IGNITE-26624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029022#comment-18029022
]
Igor Sapego commented on IGNITE-26624:
--------------------------------------
Please, ask for review from [~isapego] or [~ptupitsyn] when you are done.
> Java Client shows generic “Channel is closed” when cluster is not initialized
> -----------------------------------------------------------------------------
>
> Key: IGNITE-26624
> URL: https://issues.apache.org/jira/browse/IGNITE-26624
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Egor Kuts
> Assignee: Egor Kuts
> Priority: Minor
> Labels: ignite-3
>
> 1. Start a cluster with the thin client endpoint enabled (10800).
> 2. Do not initialize the cluster via management handler
> /management/v1/cluster/init
> 3. From a Java app, create a thin client and connect to it.
> 4. Observe a generic exception: {{{}Caused by:
> org.apache.ignite.client.IgniteClientConnectionException: IGN-CLIENT-1
> Channel is closed{}}}.
> Packet capture shows:
> * 3-way handshake
> * Server sends FIN right away
> * Client sends data, server replies RST
> Proposal fix:
> Call
> org.apache.ignite.client.handler.ClientInboundMessageHandler#handshakeError
> on the server side and pass a proper exception
> Motivation:
> Improve developer experience: users can’t tell why the connection fails.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
