[
https://issues.apache.org/jira/browse/AMBARI-17758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380949#comment-15380949
]
Hadoop QA commented on AMBARI-17758:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818413/AMBARI-17758.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7890//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7890//console
This message is automatically generated.
> LogSearch Integration NullPointerException when LogSearch connection not
> available
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-17758
> URL: https://issues.apache.org/jira/browse/AMBARI-17758
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17758.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The following NullPointerException can occur intermittently in the LogSearch
> integration code in the Ambari REST layer:
> {code}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService.getLogFileTailURI(LogSearchDataRetrievalService.java:159)
> at
> org.apache.ambari.server.controller.logging.LoggingSearchPropertyProvider.populateResources(LoggingSearchPropertyProvider.java:92)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:155)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:500)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:454)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor255.invoke(Unknown Source)
> {code}
> While the code that calls the LogSearchDataRetrievalService already has a
> check to determine if the LoggingRequestHelper is available (non-null), there
> is a change that a service might be stopped or crashes unexpected in between
> the initial check and this call.
> This is usually an intermittent exception.
> The LogSearchDataRetrievalService should be updated to include a check for
> null when attempting to access the LoggingRequestHelper implementation.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
