[ 
https://issues.apache.org/jira/browse/IGNITE-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kukushkin reassigned IGNITE-8097:
----------------------------------------

    Assignee: Alexey Kukushkin

> Java thin client: throw handshake exception on connect phase
> ------------------------------------------------------------
>
>                 Key: IGNITE-8097
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8097
>             Project: Ignite
>          Issue Type: Task
>          Components: thin client
>            Reporter: Vladimir Ozerov
>            Assignee: Alexey Kukushkin
>            Priority: Major
>             Fix For: 2.5
>
>
> Currently a call to {{Ignition.startClient}} return client instance even if 
> we know for sure that connection is not usable. Real exception (e.g. protocol 
> mismatch, auth error, etc.) is thrown on attempt to execute first operation 
> on the client. This is bad UX - use may think that everything is OK for a 
> long time.
> Instead, connection should be established eagerly in {{startClient}}, any 
> exception should be propagated to the user immediately.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to