Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B2A6910607 for ; Fri, 4 Apr 2014 15:16:30 +0000 (UTC) Received: (qmail 11535 invoked by uid 500); 4 Apr 2014 15:16:28 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 11347 invoked by uid 500); 4 Apr 2014 15:16:24 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 11280 invoked by uid 99); 4 Apr 2014 15:16:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2014 15:16:17 +0000 Date: Fri, 4 Apr 2014 15:16:16 +0000 (UTC) From: "Myroslav Papirkovskyy (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-5319) Investigate how we can log all exceptions rather than getting log that asks to call getNextException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy resolved AMBARI-5319. ------------------------------------------- Resolution: Fixed Pushed to trunk > Investigate how we can log all exceptions rather than getting log that asks to call getNextException > ---------------------------------------------------------------------------------------------------- > > Key: AMBARI-5319 > URL: https://issues.apache.org/jira/browse/AMBARI-5319 > Project: Ambari > Issue Type: Bug > Components: controller > Affects Versions: 1.5.0 > Reporter: Myroslav Papirkovskyy > Assignee: Myroslav Papirkovskyy > Fix For: 1.5.1 > > > At times when Ambari Server hits a db error we see the log as follows: > {noformat} > aused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.DatabaseException > Internal Exception: java.sql.BatchUpdateException: Batch entry 0 DELETE FROM hostcomponentstate WHERE ((((component_name = 'JOBTRACKER') AND (host_name = 'hadoop2.tsh.thomson.com')) AND (cluster_id = '1')) AND (service_name = 'MAPREDUCE')) was aborted. Call getNextException to see the cause. > Error Code: 0 > Call: DELETE FROM hostcomponentstate WHERE ((((component_name = ?) AND (host_name = ?)) AND (cluster_id = ?)) AND (service_name = ?)) > bind => [4 parameters bound] > Query: DeleteObjectQuery(org.apache.ambari.server.orm.entities.HostComponentDesiredStateEntity@8963a385) > at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:333) > at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1501) > {noformat} > The log states Call getNextException to see the cause. -- This message was sent by Atlassian JIRA (v6.2#6252)