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

Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2014/05/23 14:02:02 UTC

[jira] [Commented] (ZOOKEEPER-1512) Reduce log level of missing ZookeeperSaslClient Security Exception

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

Rakesh R commented on ZOOKEEPER-1512:
-------------------------------------

We have system property "zookeeper.sasl.client" available in ZooKeeper client which can be turned off to avoid this checks and unnecessary logging. By default this is on. Please see ZOOKEEPER-1657 for more details.

> Reduce log level of missing ZookeeperSaslClient Security Exception
> ------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1512
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1512
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>            Reporter: Micah Whitacre
>
> When running the Java client you frequently get messages like the following:
> org.apache.zookeeper.client.ZooKeeperSaslClient SecurityException: java.lang.SecurityException: Unable to locate a login configuration occurred when trying to find JAAS configuration.
> In cases where we don't want this configuration enabled, the logs get spammed with this message.  It's scope should lowered to debug/trace to prevent flooding logs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)