[
https://issues.apache.org/jira/browse/GEODE-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596745#comment-16596745
]
ASF subversion and git services commented on GEODE-5661:
--------------------------------------------------------
Commit 7aee737d89a6e9cbec7c7759a75a83ab9ba29965 in geode's branch
refs/heads/windows-heavy-lifter from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7aee737 ]
GEODE-5661: Pulse does not work when legacy SSL options are used (#2401)
> Pulse does not work when legacy SSL options are used
> ----------------------------------------------------
>
> Key: GEODE-5661
> URL: https://issues.apache.org/jira/browse/GEODE-5661
> Project: Geode
> Issue Type: Bug
> Components: pulse
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to GEODE-5230, if the legacy SSL configuration options are used,
> ({{cluster-ssl-*}}, {{jmx-manager-ssl-*}}, etc.), then Pulse does not work
> correctly and a user will see an error similar to the following in the UI:
> {noformat}
> Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root
> exception is java.rmi.ConnectIOException: error during JRMP connection
> establishment; nested exception is: javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
