[ https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716375#comment-16716375 ]
Sergey Chugunov commented on IGNITE-10300: ------------------------------------------ [~agoncharuk], I agree with [~voropava] here: we already have a section dedicated to analyze exception's cause and returning proper error code, it is just a few lines below. Instead of returning error code from another place in the method body why not to trigger an existing code by throwing an exception? > control.sh: incorrect error message after three tries on unsuccessful > authorization. > ------------------------------------------------------------------------------------ > > Key: IGNITE-10300 > URL: https://issues.apache.org/jira/browse/IGNITE-10300 > Project: Ignite > Issue Type: Bug > Reporter: Pavel Voronkin > Assignee: Pavel Voronkin > Priority: Major > Fix For: 2.8 > > > 1. start grid with securirty enabled > 2. try to issue control.sh --cache > authentication credentials asked > 3. enter incorrect credentials three times > expected: Authentication error printed and logged > actual: Latest topology update failed error printed > {noformat} > IGNITE_HOME=`pwd` bin/control.sh --cache list . > Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7] > 2018 Copyright(C) Apache Software Foundation > User: mshonichev > -------------------------------------------------------------------------------- > Authentication error, try connection again. > user: > password: > Authentication error, try connection again. > user: > password: > Authentication error, try connection again. > user: > password: > Authentication error. > Error: Latest topology update failed. > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)