Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8817D10AC1 for ; Mon, 24 Feb 2014 17:34:30 +0000 (UTC) Received: (qmail 65554 invoked by uid 500); 24 Feb 2014 17:34:25 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 65390 invoked by uid 500); 24 Feb 2014 17:34:21 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 65354 invoked by uid 99); 24 Feb 2014 17:34:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 17:34:20 +0000 Date: Mon, 24 Feb 2014 17:34:20 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2390) TraceProxy.trace should not throw InvocationTargetException 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/ACCUMULO-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910551#comment-13910551 ] ASF subversion and git services commented on ACCUMULO-2390: ----------------------------------------------------------- Commit 2829426618b6e7d1487a4c88dd7b09186b9898d5 in accumulo's branch refs/heads/1.6.0-SNAPSHOT from [~mdrob@cloudera.com] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=2829426 ] ACCUMULO-2390 InvocationTargetEx in TraceProxy Handle InvocationTargetException specifically in TraceProxy, instead of letting it get propogated up the call stack. In some cases this is very bad as it turned into an UndeclaredThrowableException and made debugging more difficult than necessary. Added unit test to verify behaviour. > TraceProxy.trace should not throw InvocationTargetException > ----------------------------------------------------------- > > Key: ACCUMULO-2390 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2390 > Project: Accumulo > Issue Type: Bug > Components: trace > Affects Versions: 1.4.4, 1.5.0 > Reporter: Mike Drob > Assignee: Mike Drob > Fix For: 1.4.5, 1.6.0, 1.5.2 > > > In {{TraceProxy.trace}} there is the following code snippet: > {code} > try { > return method.invoke(instance, args); > } catch (Throwable ex) { > ex.printStackTrace(); > throw ex; > } > {code} > When this is an InvocationTargetException, it can really mess with the calling code's exception handling logic. -- This message was sent by Atlassian JIRA (v6.1.5#6160)