accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3094) Pass back stack traces when server side exception occurs
Date Mon, 03 Aug 2015 17:45:05 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652176#comment-14652176
] 

Josh Elser commented on ACCUMULO-3094:
--------------------------------------

I just had a thought about this. If we would implement this functionality, it would be important
to wrap whatever exceptions coming out of the server with some clear naming that leaves no
room for ambiguity that this exception happened in a server and not in the client JVM.

For example, seeing a ClassNotFoundException could require two different changes: in the client
JVM or the server JVM. We would want to make sure that it is clear to the user where the error
occurred. 

> 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.8.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)

Mime
View raw message