Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 332A4DB91 for ; Wed, 8 Aug 2012 18:35:22 +0000 (UTC) Received: (qmail 97518 invoked by uid 500); 8 Aug 2012 18:35:21 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 97468 invoked by uid 500); 8 Aug 2012 18:35:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 97335 invoked by uid 99); 8 Aug 2012 18:35:21 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2012 18:35:21 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 3D553141E28 for ; Wed, 8 Aug 2012 18:35:21 +0000 (UTC) Date: Wed, 8 Aug 2012 18:35:21 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1051896774.1108.1344450921253.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1757730661.774.1344444680494.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HADOOP-8661) Stack Trace in Exception.getMessage causing oozie DB to have issues 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/HADOOP-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431276#comment-13431276 ] Suresh Srinivas commented on HADOOP-8661: ----------------------------------------- On 2.0, the stack trace may be a little different, since we have switched to protobuf RPC engine. This change was done in HADOOP-6686. So any solution needs to consider some of the discussions from that jira. > Stack Trace in Exception.getMessage causing oozie DB to have issues > ------------------------------------------------------------------- > > Key: HADOOP-8661 > URL: https://issues.apache.org/jira/browse/HADOOP-8661 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0 > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > Priority: Critical > > It looks like all exceptions produced by RemoteException include the full stack trace of the original exception in the message. This is causing issues for oozie because they store the message in their database and it is getting very large. This appears to be a regression from 1.0 behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira