You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2015/03/02 20:29:07 UTC

[jira] [Updated] (GORA-410) Change logging behavior to pass exception object to LOG methods

     [ https://issues.apache.org/jira/browse/GORA-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated GORA-410:
--------------------------------------
    Fix Version/s:     (was: 0.7)
                   0.6.1

> Change logging behavior to pass exception object to LOG methods
> ---------------------------------------------------------------
>
>                 Key: GORA-410
>                 URL: https://issues.apache.org/jira/browse/GORA-410
>             Project: Apache Gora
>          Issue Type: Improvement
>            Reporter: Gerhard Gossen
>            Assignee: Gerhard Gossen
>             Fix For: 0.6.1
>
>         Attachments: exception_logging.patch
>
>
> Throughout the codebase, exceptions are reported by logging {{e.getStackTrace().toString()}}. As {{getStackTrace}} returns an array and Java's array {{.toString}} method just returns the object ID, this means that the stack traces are effectively lost. Instead the exception should be passed to the logger in its original form as the second argument, SLF4J does the right thing with the stack trace.
> This problem was tackled in GORA-230 for AccumuloStore. The attached patch corrects all instances of the problem in the current trunk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)