You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/18 15:28:00 UTC

[jira] [Commented] (KNOX-1324) Remote Configuration Monitor should not log stacktrace when client is not configured

    [ https://issues.apache.org/jira/browse/KNOX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480802#comment-16480802 ] 

ASF subversion and git services commented on KNOX-1324:
-------------------------------------------------------

Commit 437a9a88323d0973ebdd135115ba23f8a20a6d81 in knox's branch refs/heads/master from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=437a9a8 ]

KNOX-1324 - Remote Configuration Monitor should not log stacktrace when client is not configured


> Remote Configuration Monitor should not log stacktrace when client is not configured
> ------------------------------------------------------------------------------------
>
>                 Key: KNOX-1324
>                 URL: https://issues.apache.org/jira/browse/KNOX-1324
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.0.0
>            Reporter: Phil Zampino
>            Assignee: Phil Zampino
>            Priority: Major
>             Fix For: 1.1.0
>
>
> When debug logging is enabled, the Remote Configuration Monitor failure to acquire a remote config client results in a stacktrace in gateway.log. The stacktrace is unnecessary, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)