You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Mario Kevo (Jira)" <ji...@apache.org> on 2022/06/02 13:08:00 UTC

[jira] [Resolved] (GEODE-8655) Not handling exception on SNIHostName

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

Mario Kevo resolved GEODE-8655.
-------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> Not handling exception on SNIHostName
> -------------------------------------
>
>                 Key: GEODE-8655
>                 URL: https://issues.apache.org/jira/browse/GEODE-8655
>             Project: Geode
>          Issue Type: Bug
>          Components: locator, security
>    Affects Versions: 1.13.0
>            Reporter: Mario Kevo
>            Assignee: Mario Kevo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> If we start locator with ipv6 and TLS enabled we got following error for status locator command:
>   
> {quote}mkevo@mkevo-XPS-15-9570:~/apache-geode-1.13.0/bin/locator$ _/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -server -classpath /home/mkevo/apache-geode-1.13.0/lib/geode-core-1.13.0.jar:/home/mkevo/apache-geode-1.13.0/lib/geode-dependencies.jar -Djava.net.preferIPv6Addresses=true -DgemfireSecurityPropertyFile=/home/mkevo/geode-examples/clientSecurity/example_security.properties -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 org.apache.geode.distributed.LocatorLauncher start locator --port=10334_
>   
>  gfsh>_status locator --dir=/home/mkevo/apache-geode-1.13.0/bin/locator --security-properties-file=/home/mkevo/geode-examples/clientSecurity/example_security.properties_
>  *Locator in /home/mkevo/apache-geode-1.13.0/bin/locator on mkevo-XPS-15-9570[10334] is currently not responding.*
> {quote}
>  
>  From locator logs we found only this:
> {quote}Exception in processing request from fe80:0:0:0:f83e:ce0f:5143:f9ee%2: Read timed out
> {quote}
>  
>  After adding some logs we found the following:
> {quote}{color:#1d1c1d}TcpClient.stop(): exception connecting to locator HostAndPort[/0:0:0:0:0:0:0:0:10334]java.lang.IllegalArgumentException: Contains non-LDH ASCII characters{color}
> {quote}
> **
>  It fails on creating SNIHostName from hostName(_setServerNames_ in SocketCreator.java) as it not handling above exception.
>   
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)