You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2015/04/20 21:51:00 UTC

[jira] [Updated] (KNOX-466) Log exception stack traces at INFO level when they reach gateway servlet

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

Kevin Minder updated KNOX-466:
------------------------------
    Issue Type: Improvement  (was: Bug)

> Log exception stack traces at INFO level when they reach gateway servlet
> ------------------------------------------------------------------------
>
>                 Key: KNOX-466
>                 URL: https://issues.apache.org/jira/browse/KNOX-466
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 0.5.0
>            Reporter: Kevin Minder
>            Assignee: Kevin Minder
>             Fix For: 0.6.0
>
>
> Currently exception that reach the gateway servlet only have their full stack traces logged when the logging level is DEBUG or finer.  This often hampers diagnosability as it forces an issue to be reproduced after changing the log level and restarting the server.  Exceptions reaching the gateway servlet should have their full stack traces logged at the default level of INFO.



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