[ https://issues.apache.org/jira/browse/ZOOKEEPER-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427009#comment-13427009 ]
Hudson commented on ZOOKEEPER-1510: ----------------------------------- Integrated in ZooKeeper-trunk #1633 (See [https://builds.apache.org/job/ZooKeeper-trunk/1633/]) ZOOKEEPER-1510. Should not log SASL errors for non-secure usage (Todd Lipcon via phunt) Missed a bit in the prior commit (Revision 1368299) ZOOKEEPER-1510. Should not log SASL errors for non-secure usage (Todd Lipcon via phunt) (Revision 1368267) Result = SUCCESS phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1368299 Files : * /zookeeper/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1368267 Files : * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java > Should not log SASL errors for non-secure usage > ----------------------------------------------- > > Key: ZOOKEEPER-1510 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1510 > Project: ZooKeeper > Issue Type: Improvement > Components: java client > Affects Versions: 3.4.3 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Minor > Fix For: 3.4.4, 3.5.0 > > Attachments: zookeeper-1510.txt, zookeeper-1510.txt > > > Since SASL support was added, all connections with non-secure clients have > started logging messages like: > 2012-07-01 02:13:34,986 WARN org.apache.zookeeper.client.ZooKeeperSaslClient: > SecurityException: java.lang.SecurityException: Unable to locate a login > configuration occurred when trying to find JAAS configuration. > 2012-07-01 02:13:34,986 INFO org.apache.zookeeper.client.ZooKeeperSaslClient: > Client will not SASL-authenticate because the default JAAS configuration > section 'Client' could not be found. If you are not using SASL, you may > ignore this. On the other hand, if you expected SASL to work, please fix your > JAAS configuration. > Despite the "you may ignore this" qualifier, I've seen a lot of users > confused by this message. Instead, it would be better to either log at DEBUG > level, or piggy back the SASL information onto the "Opening socket > connection" message (eg "Opening socket connection to X:2181. Will not use > SASL because no configuration was located.") -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira