Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 15 Sep 2016 16:14:20 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13005202.1473955676000.581385.1473956060580@Atlassian.JIRA>
In-Reply-To: <JIRA.13005202.1473955676000@Atlassian.JIRA>
References: <JIRA.13005202.1473955676000@Atlassian.JIRA> <JIRA.13005202.1473955676557@arcas>
Subject: [jira] [Updated] (AMBARI-18404) Upgrade Summary Endpoint Throws
 NPEs Due To JPA Cached Entities With Missing IDs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 15 Sep 2016 16:14:22 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-18404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-18404:
-------------------------------------
    Fix Version/s:     (was: 2.5.0)
                   2.4.2

> Upgrade Summary Endpoint Throws NPEs Due To JPA Cached Entities With Missing IDs
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-18404
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18404
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.4.2
>
>
> When creating an upgrade, the {{upgrades_summary}} endpoint sometimes returns a NPE. 
> STR:
> - Start an upgrade
> - Force an error (remove {{hdp-select}})
> - Wait for error in upgrade, and then make a request to {{upgrades_summary}}
> {code}
> HostRoleCommandEntity mostRecentFailure = s_hostRoleCommandDAO.findMostRecentFailure(upgradeRequestId);
> {code}
> And its requestId is null
> DB is fine
> {code}
> ambari=> select request_id, task_id, status, role, role_command, custom_command_name from host_role_command where task_id = 504;
>  request_id | task_id |      status      |    role     |  role_command  | custom_command_name
> ------------+---------+------------------+-------------+----------------+---------------------
>          45 |     504 | HOLDING_TIMEDOUT | NODEMANAGER | CUSTOM_COMMAND | STOP
> (1 row)
> {code}
> Problem is with query,
> {code}
>     TypedQuery<HostRoleCommandEntity> query = entityManagerProvider.get().createNamedQuery(
>         "HostRoleCommandEntity.findTasksByStatusesOrderByIdDesc", HostRoleCommandEntity.class);
>     query.setParameter("requestId", requestId);
>     query.setParameter("statuses", HostRoleStatus.STACK_UPGRADE_FAILED_STATUSES);
>     List<HostRoleCommandEntity> results = query.getResultList();
> ...
>     HostRoleCommandEntity candidate = results.get(0);
> {code}
> since "candidate" has no requestId.
> However, HostRoleCommandEntity.java defines the query like so,
> {code}
> @NamedQuery(name = "HostRoleCommandEntity.findTasksByStatusesOrderByIdDesc", query = "SELECT task FROM HostRoleCommandEntity task WHERE task.requestId = :requestId AND task.status IN :statuses ORDER BY task.taskId DESC"),
> {code}
> so the "task" object should have a request_id, especially since it's defined to be non-nullable,
> {code}
>   @Column(name = "request_id", insertable = false, updatable = false, nullable = false)
>   @Basic
>   private Long requestId;
> {code}


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