LDAP-230: Pool Validation polluting logs with "IOException: connection closed" stacktrace even though it is handled gracefully by framework

Lowered to log level to debug.
This commit is contained in:
Mattias Hellborg Arthursson
2013-08-14 14:29:22 +02:00
parent 74380e1fc9
commit 97cbfbedda

View File

@@ -16,15 +16,15 @@
package org.springframework.ldap.pool.validation;
import javax.naming.NamingEnumeration;
import javax.naming.directory.DirContext;
import javax.naming.directory.SearchControls;
import org.apache.commons.lang.Validate;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.springframework.ldap.pool.DirContextType;
import javax.naming.NamingEnumeration;
import javax.naming.directory.DirContext;
import javax.naming.directory.SearchControls;
/**
* Default {@link DirContext} validator that executes {@link DirContext#search(String, String, SearchControls)}. The
* name, filter and {@link SearchControls} are all configurable. There is no special handling for read only versus
@@ -174,11 +174,13 @@ public class DefaultDirContextValidator implements DirContextValidator {
}
}
catch (Exception e) {
this.logger.warn("DirContext '" + dirContext + "' failed validation with an exception.", e);
if(this.logger.isDebugEnabled()) {
this.logger.debug("DirContext '" + dirContext + "' failed validation with an exception.", e);
}
}
if (this.logger.isInfoEnabled()) {
this.logger.info("DirContext '" + dirContext + "' failed validation.");
if (this.logger.isDebugEnabled()) {
this.logger.debug("DirContext '" + dirContext + "' failed validation.");
}
return false;
}