[
https://issues.apache.org/jira/browse/KNOX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801804#comment-17801804
]
ASF subversion and git services commented on KNOX-2993:
-------------------------------------------------------
Commit 050e2ceaad399d71f00f6a8bd3c92d02f5f1dffa in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=050e2ceaa ]
KNOX-2993 - Logging error stack trace at INFO level when failed to parse a
descriptor (#827)
> Show error stack trace when simple descriptor handler fails to parse a
> descriptor
> ---------------------------------------------------------------------------------
>
> Key: KNOX-2993
> URL: https://issues.apache.org/jira/browse/KNOX-2993
> Project: Apache Knox
> Issue Type: Task
> Components: Server
> Affects Versions: 2.0.0, 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, the error stack trace is shown in gateway.log only, if the
> {{org.apache.knox.gateway}} log level is set to {{DEBUG}}:
> {noformat}
> @Message( level = MessageLevel.ERROR, text = "An error occurred while
> processing {0} : {1}" )
> void simpleDescriptorHandlingError(String simpleDesc,
> @StackTrace(level = MessageLevel.DEBUG)
> Exception e);
> {noformat}
> This makes our lives hard when dealing with errors related to events coming
> from CM configuration monitoring.
> I recommend showing this information even on {{INFO}} level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
