You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2013/08/19 23:31:48 UTC

[jira] [Commented] (AMBARI-2941) Ambari server gets auth exception while getting JMX metrics from namenode in secure cluster.

    [ https://issues.apache.org/jira/browse/AMBARI-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744256#comment-13744256 ] 

Nate Cole commented on AMBARI-2941:
-----------------------------------

* This paradigm (DCL) is no longer necessary:
{noformat}
+  if (sslSocketFactory == null) {
+    synchronized (this) {
+      if (sslSocketFactory == null) {
{noformat}
You already made sslSocketFactory volatile, and the compiler is smarter than it used to be, making the DCL unnecessary.  You should be able to single-check it.
                
> Ambari server gets auth exception while getting JMX metrics from namenode in secure cluster.
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-2941
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2941
>             Project: Ambari
>          Issue Type: Task
>         Environment: Ambari server set up to monitor and manage a hadoop cluster secured with keberos authentication
>            Reporter: Dilli Arumugam
>            Assignee: Dilli Arumugam
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-2941.patch
>
>
> After applying secure configs to core-site.xml for http client authentication, Ambari server is not able to authenticate to get JMX metrics.
> Ambari server log:
> 17:00:08,799 ERROR pool-1-thread-1861 JMXPropertyProvider:446 - Caught exception getting JMX metrics : Server returned HTTP response code: 401 for URL: http://dev01.hortonworks.com:50070/jmx
> 17:00:10,759 ERROR pool-1-thread-1888 JMXPropertyProvider:446 - Caught exception getting JMX metrics : Connection refused

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira