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

Hadoop QA commented on AMBARI-9823:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12707362/AMBARI-9823.patch.2
  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 1 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/2142//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2142//console

This message is automatically generated.

> Alert Notifications Are Not Received Without Restarting Ambari Server
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-9823
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9823
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9823.patch, AMBARI-9823.patch.2
>
>
> There seems to be an issue with EclipseLink and nested entities where the 
> relationships are not refreshed from the database correctly. This causes a 
> problem sending out alert notices for alert groups because the target lookup 
> doesn't return the correct entities.
> Restarting Ambari Server fixes the issue. 



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

Reply via email to