ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <>
Subject [jira] [Created] (AMBARI-16965) Exception while detecting JMX protocol for HISTORYSERVER
Date Tue, 31 May 2016 11:26:12 GMT
Andrew Onischuk created AMBARI-16965:

             Summary: Exception while detecting JMX protocol for HISTORYSERVER
                 Key: AMBARI-16965
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.4.0
         Attachments: AMBARI-16965.patch

Secured cluster with HDP 2.5. (also installed Ranger but I'm not sure that it
influences on this)  
I see a lot of exception in ambari server logs:

    25 May 2016 16:50:16,982  INFO [pool-7-thread-26] AbstractProviderModule:1184 - Defaulting
JMX to HTTP protocol for  for clusterName = c1, componentName = HISTORYSERVERHISTORYSERVER
    25 May 2016 16:50:23,617  INFO [pool-7-thread-28] AbstractProviderModule:1182 - Exception
while detecting JMX protocol for clusterName = c1, componentName = HISTORYSERVER
            at org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocolString(
            at org.apache.ambari.server.controller.internal.AbstractProviderModule.getJMXProtocol(
            at org.apache.ambari.server.controller.jmx.JMXPropertyProvider.getJMXProtocol(
            at org.apache.ambari.server.controller.jmx.JMXPropertyProvider.populateResource(
            at org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$
            at org.apache.ambari.server.controller.metrics.ThreadPoolEnabledPropertyProvider$
            at java.util.concurrent.Executors$
            at java.util.concurrent.ThreadPoolExecutor.runWorker(
            at java.util.concurrent.ThreadPoolExecutor$

It appears every few seconds

This message was sent by Atlassian JIRA

View raw message