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 A2CB211D77 for ; Wed, 3 Sep 2014 01:55:52 +0000 (UTC) Received: (qmail 32751 invoked by uid 500); 3 Sep 2014 01:55:52 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 32711 invoked by uid 500); 3 Sep 2014 01:55:52 -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 32697 invoked by uid 99); 3 Sep 2014 01:55:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2014 01:55:52 +0000 Date: Wed, 3 Sep 2014 01:55:52 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3094) Pass back stack traces when server side exception occurs 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-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119182#comment-14119182 ] Christopher Tubbs commented on ACCUMULO-3094: --------------------------------------------- Yeah, I like the idea of a development mode, like is common for web servers / frameworks, as [~elserj] points out, but the default should be off, like [~kturner] said. This should be a server-side configuration (general.server.stacktrace.verbosity=(none, partial, full)?). Clients shouldn't be able to choose how much detail is returned. It should be a mode that an admin chooses, either with a restart, or (maybe) a live configuration change. > Pass back stack traces when server side exception occurs > --------------------------------------------------------- > > Key: ACCUMULO-3094 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3094 > Project: Accumulo > Issue Type: Bug > Reporter: Keith Turner > Fix For: 1.7.0 > > > Was discussing ACCUMULO-3092 w/ [~dlmarion] and the issue of why more info about server side exceptions was not transmitted back to client came up. This was a concious design decision made in Accumulo to avoid unintentionally leaking information to the client. The main concern is the exception message on the server side, that message could have been constructed w/ data from Accumulo. > We discussed the possibility of dropping the exception message[s] and sending the stack trace[s] back to the client side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)