[
https://issues.apache.org/jira/browse/ZOOKEEPER-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044388#comment-15044388
]
Raul Gutierrez Segales commented on ZOOKEEPER-2300:
---------------------------------------------------
Sadly the test output is not available anymore, but I presume the failure is
unrelated. Given the change is very self-contained and the attached test passes
locally for me, I'll go ahead and apply.
> Expose SecureClientPort and SecureClientAddress JMX properties
> --------------------------------------------------------------
>
> Key: ZOOKEEPER-2300
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2300
> Project: ZooKeeper
> Issue Type: Improvement
> Components: jmx
> Affects Versions: 3.5.0
> Reporter: Arshad Mohammad
> Assignee: Arshad Mohammad
> Fix For: 3.5.2
>
> Attachments: ZOOKEEPER-2300-01.patch
>
>
> ZooKeeper currently exposes ClientPort and ClientAddress JMX properties.
> Same way we should expose SecureClientPort and SecureClientAddress.
> The values for these two properties will be decided based on the configured
> value of secureClientPort and secureClientPortAddress
> The value of SecureClientPort will be:
> secureClientPort {color:blue}(if secureClientPort is configured){color}
> empty string {color:blue}(If secureClientPort is not configured){color}
> The value of SecureClientAddress will be:
> secureClientPortAddress:secureClientPort {color:blue}(if both
> secureClientPort and secureClientPortAddress are configured){color}
> 0.0.0.0:secureClientPort or 0:0:0:0:0:0:0:0:secureClientPort {color:blue}(if
> only secureClientPort is configured){color}
> empty string {color:blue}(If secureClientPort is not configured){color}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
