[jira] [Commented] (AMBARI-9953) Ambari Metrics monitor restart failed with error JAVA_HOME is not set

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-9953:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12703079/AMBARI-9953.0.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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/1949//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1949//console

This message is automatically generated.

> Ambari Metrics monitor restart failed with error JAVA_HOME is not set
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-9953
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9953
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-metrics, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Florian Barca
>            Assignee: Florian Barca
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9953.0.patch
>
>
> AMS Collector fails to restart if the installation of a certain upstream component failed. In this case, start() is skipped, and install() is followed by restart() immediately. restart() being implemented by a stop()+start() sequence, it results that stop() needs to make sure that the service is configured prior to invoking any low-level scripts.



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