[
https://issues.apache.org/jira/browse/KNOX-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195224#comment-14195224
]
ASF subversion and git services commented on KNOX-466:
------------------------------------------------------
Commit 0edaec6e33f68f6fe68b2e63e6f867401f194c2d in knox's branch
refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=0edaec6 ]
KNOX-466: Log exception stack traces at INFO level when they reach gateway
servlet
> 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: Bug
> 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)
