gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GORA-410) Change logging behavior to pass exception object to LOG methods
Date Sun, 22 Feb 2015 21:49:12 GMT

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

Lewis John McGibbney updated GORA-410:
--------------------------------------
    Issue Type: Improvement  (was: Bug)

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

Mime
View raw message