[jira] [Commented] (GEODE-9880) Cluster with multiple locators in an environment with no host name resolution, leads to null pointer exception

["Tigran Ghahramanyan (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456357#comment-17456357 ] 

Tigran Ghahramanyan commented on GEODE-9880:
--------------------------------------------

Experimenting with 

_builder.setHostnameForClients();_

And setting the corresponding IP address represented as a string to override the host name for each locator, works around the above described problem, allowing the cluster to start.

> Cluster with multiple locators in an environment with no host name resolution, leads to null pointer exception
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-9880
>                 URL: https://issues.apache.org/jira/browse/GEODE-9880
>             Project: Geode
>          Issue Type: Bug
>          Components: locator
>    Affects Versions: 1.12.5
>            Reporter: Tigran Ghahramanyan
>            Priority: Major
>
> In our use case we have two locators that are initially configured with IP addresses, but _AutoConnectionSourceImpl.UpdateLocatorList()_ flow keeps on adding their corresponding host names to the locators list, while these host names are not resolvable.
> Later in {_}AutoConnectionSourceImpl.queryLocators(){_}, whenever a client tries to use such non resolvable host name to connect to a locator it tries to establish a connection to {_}socketaddr=0.0.0.0{_}, as written in {_}SocketCreator.connect(){_}. Which seems strange.
> Then, if there is no locator running on the same host, the next locator in the list is contacted, until reaching a locator contact configured with IP address - which succeeds eventually.
> But, when there happens to be a locator listening on the same host, then we have a null pointer exception in the second line below, because _inetadd=null_
> _socket.connect(sockaddr, Math.max(timeout, 0)); // sockaddr=0.0.0.0, connects to a locator listening on the same host_
> _configureClientSSLSocket(socket, inetadd.getHostName(), timeout); // inetadd = null_
>  
> As a result, the cluster comes to a failed state, unable to recover.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)