Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Subject: Re: Logging LDAP requests
From: Przemyslaw Rudzki <erace@erace.pl>
To: users@directory.apache.org
In-Reply-To: <a32f6b020710081938k2d719715icdea2b2f9e24339c@mail.gmail.com>
References: <096b01c80a10$b8e159f0$1e57c7d0@miti.local>
	 <a32f6b020710081938k2d719715icdea2b2f9e24339c@mail.gmail.com>
Content-Type: text/plain
Date: Tue, 09 Oct 2007 09:45:04 +0200
Message-Id: <1191915904.6084.9.camel@erace>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

BTW. How can I get rid of those warnings when running ApacheDS inside
JBoss?

...
09:41:27,128 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute
1.3.6.1.4.1.18060.0.4.1.2.3
09:41:27,133 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute objectClass
09:41:27,136 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute
1.3.6.1.4.1.18060.0.4.1.2.1
09:41:27,138 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute
1.3.6.1.4.1.18060.0.4.1.2.6
09:41:27,140 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute
1.3.6.1.4.1.18060.0.4.1.2.7
09:41:27,142 INFO  [STDOUT] [09:41:27] WARN
[org.apache.directory.server.core.partition.impl.btree.BTreePartition] -
Using default cache size of 100 for index on attribute
1.3.6.1.4.1.18060.0.4.1.2.4
...

I have tried the following stuff:

log4j.logger.org.apache.directory.server.core.*=ERROR
log4j.logger.org.apache.directory.server.core.partition.impl.btree.BTreePartition=INFO

But it does not work as expected.

/p

On Mon, 2007-10-08 at 22:38 -0400, Alex Karasulu wrote:
> On 10/8/07, Olivier Schmitt <schmitt@metaintegration.net> wrote:
> >
> > I am a new user of Apache Directory Server 1.5, and so far I love it!
> > It is pretty easy to use and configure, and the Studio UI is nice too.
> 
> 
> Cool beans!
> 
> Now, I am trying figure out why my business app cannot connect to it.
> > In order to better understand what is going wrong, I would like to enable
> > logging of LDAP requests coming into the server.
> 
> 
> It should not matter but sometimes Windows does odd things with logging
> so could you let us know if you're running on windows or not?
> 
> As recommended on the page
> > http://directory.apache.org/apacheds/1.5/145-configure-logging.html
> > I tinkered with the logging parameters, but could not find appropriate
> > level
> > of detail I am interested in, it would report either nothing, or a huge
> > lot
> > of things I cant make sense of.
> 
> 
> Right you probably set the global log level and that just turned on
> everything.
> 
> Is there a simple way to set the logging to display something like this?
> > - LDAP server received BIND request (+details of bind request)
> > - LDAP server received SEARCH request (+details or search request)
> >
> 
> I would leave the global log level on WARN and add the following lines to
> your
> log4j.properties then tweak (comment out) them depending on what you're
> interested
> in:
> 
> log4j.logger.org.apache.directory.server.ldap=INFO
> #General Frontend Handling
> log4j.logger.org.apache.directory.server.ldap.support.bind=INFO
> #For SASL binds
> log4j.logger.org.apache.directory.server.ldap.support.BindHandler=INFO
> #For Simple binds
> log4j.logger.org.apache.directory.server.ldap.support.SearchHandler=INFO
> 
> There's more to it if you want to get into the internals.  I would first
> write a simple
> application and make sure you can connect to the server or just use Studio
> to do
> it to confirm it is configured properly and go from there.
> 
> HTH,
> Alex