| Enrique Rodriguez 2007-06-06, 1:11 am |
| On 6/5/07, elecharny-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org <elecharny-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
> Author: elecharny
> Date: Tue Jun 5 17:09:01 2007
> New Revision: 544690
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=544690
> Log:
> Replaced the stack trace by a simple message. As such a message
> is now dumped for each bind request, with a full stack trace we will
> have a gigantic log file on a heavy loaded server
> ...
> @@ -71,7 +71,7 @@
> saslProps.put( "com.sun.security.sasl.digest.realm", getActiveRealms( config ) );
> session.setAttribute( "saslProps", saslProps );
>
> - session.setAttribute( "saslHost", config.getSaslHost() );
> + session.setAttribute( "saslProps", config.getSaslHost() );
> session.setAttribute( "baseDn", config.getSearchBaseDn() );
>
> Set activeMechanisms = getActiveMechanisms( config );
> @@ -86,7 +86,7 @@
> catch ( ServiceConfigurationException sce )
> {
> activeMechanisms.remove( "GSSAPI" );
> - log.warn( sce.getMessage(), sce );
> + log.warn( sce.getMessage() );
Changing the saslHost/saslProps attribute is a mistake. It breaks the
SaslBindITest. Can you please revert it? If you intended a saslProps
change you also didn't note it in your commit message nor run the
integration tests.
While you're at it, can you revert the addition of the max time limit
and max size limit to StartupConfig/MutableStartupConfig? There are
now do-nothing getter/setters there.
Enrique
|