[
https://issues.apache.org/jira/browse/GORA-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved GORA-410.
---------------------------------------
Resolution: Fixed
commit 65d6c7ac29d2cc041d067e5e7f0857936a7529d7
Author: Lewis John McGibbney <lewis.j.mcgibb...@jpl.nasa.gov>
Date: Sun Feb 22 13:48:38 2015 -0800
GORA-410 Change logging behavior to pass exception object to LOG methods
Thank you very much [~gerhard.gossen], great patch.
> 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)
