Dmytro Sen created AMBARI-9262:
----------------------------------

             Summary: AMS: stack traces printed to ambari-server.log
                 Key: AMBARI-9262
                 URL: https://issues.apache.org/jira/browse/AMBARI-9262
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.0.0
            Reporter: Dmytro Sen
            Assignee: Dmytro Sen
             Fix For: 2.0.0


Metrics system got in a bad state so ambari server was unable to retrieve 
metrics. exceptions were bring printed to the ambari-server log, even though, 
the message is warn.
Should avoid printing stack trace to log unless in DEBUG. This log entry should 
be an error
{noformat}
09:59:48,274  WARN [qtp170173019-19] MetricsPropertyProvider:187 - Error 
getting timeline metrics.
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:152)
        at java.net.SocketInputStream.read(SocketInputStream.java:122)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
        at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1323)
        at 
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
        at 
org.apache.ambari.server.controller.internal.URLStreamProvider.processURL(URLStreamProvider.java:177)
        at 
org.apache.ambari.server.controller.internal.URLStreamProvider.readFrom(URLStreamProvider.java:105)
        at 
org.apache.ambari.server.controller.internal.URLStreamProvider.readFrom(URLStreamProvider.java:110)
{noformat}



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

Reply via email to