You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2018/03/08 17:39:00 UTC
[jira] [Updated] (AMBARI-23129) Multiple issues while executing
Ambari server upgrade to Ambari 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas updated AMBARI-23129:
----------------------------------
Summary: Multiple issues while executing Ambari server upgrade to Ambari 2.7.0 (was: NPE while initializing Ambari server upgrade to Ambari 2.7.0)
> Multiple issues while executing Ambari server upgrade to Ambari 2.7.0
> ---------------------------------------------------------------------
>
> Key: AMBARI-23129
> URL: https://issues.apache.org/jira/browse/AMBARI-23129
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Fix For: 2.7.0
>
>
> An NPE is thrown will initializing the Ambari server upgrade catalog:
> {code:title=com.google.inject.persist.jpa.JpaPersistService#begin}
> public void begin() {
> Preconditions.checkState(null == this.entityManager.get(), "Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between.");
> this.entityManager.set(this.emFactory.createEntityManager());
> }
> {code}
> {{this.emFactory}} is {{null}}.
> *Cause*
> {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order of operations in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}.
> *Solution*
> Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)