geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-417) deprecated ssl-* gemfire properties should not be allowed with cluster-ssl-* properties
Date Fri, 16 Oct 2015 23:39:05 GMT
Darrel Schneider created GEODE-417:
--------------------------------------

             Summary: deprecated ssl-* gemfire properties should not be allowed with cluster-ssl-*
properties
                 Key: GEODE-417
                 URL: https://issues.apache.org/jira/browse/GEODE-417
             Project: Geode
          Issue Type: Bug
          Components: core
            Reporter: Darrel Schneider
            Assignee: Darrel Schneider
            Priority: Minor


The ssl-* gemfire properties were deprecated in 8.0 in favor of the cluster-ssl-* properties.
If you specify both then you are supposed to get an error if they are not the same. But instead
you only get the error if they are both not equal to the default value. For the properties
whose values are String the equality check does an identity check against the default value
which will never be true. For the properties whose values are Boolean the equality check is
ok but the logic is wrong. It should be asking if both of them were set to the same value;
not if both of them are not equal to the default.
The same problem exists for jmx-manager-ssl which was deprecated in favor of jmx-manager-ssl-enabled.
Another related problem is that if you do get the exception it has a message that says "...Prefer
way is to use" which is bad english.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message