You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Gang Yan (Jira)" <ji...@apache.org> on 2020/01/06 18:56:00 UTC
[jira] [Commented] (GEODE-7583) "status locator --name/--dir" is
not working properly when locator ssl is enabled
[ https://issues.apache.org/jira/browse/GEODE-7583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009097#comment-17009097 ]
Gang Yan commented on GEODE-7583:
---------------------------------
[~jmcallister@pivotal.io]
Hi Joey
there might be some docs update for this command.
> "status locator --name/--dir" is not working properly when locator ssl is enabled
> ---------------------------------------------------------------------------------
>
> Key: GEODE-7583
> URL: https://issues.apache.org/jira/browse/GEODE-7583
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
> Affects Versions: 1.8.0, 1.9.0, 1.10.0, 1.11.0
> Reporter: Jinmei Liao
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> in 1.8:
> 1. start a locator with ssl enabled
> 2. "status locator --dir" or "status locator --name" would trigger such error messages in the locator log:
> {quote}[info 2019/12/16 08:57:39.958 PST locator <locator request thread 1> tid=0x23] Exception in processing request from 10.118.20.75
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at org.apache.geode.internal.net.SocketCreator.handshakeIfSocketIsSSL(SocketCreator.java:981)
> at org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:346)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
> In develop branch: the gfsh output would be a strange ClassCastException. It's definitely broken on develop
--
This message was sent by Atlassian Jira
(v8.3.4#803005)