directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1871) Logging Not Working in M14
Date Wed, 24 Jul 2013 07:07:50 GMT

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

Pierre-Arnaud Marcelot commented on DIRSERVER-1871:
---------------------------------------------------

Hi Jonathan,

I checked most of the ApacheDS installers (Binary, Debian, OS X, Archive zip and tar.gz) and
logging works for all them.

Now, changing the root logger level is not enough to have logs showing, you also need to change
the log level on the particular logs you're interested in and we have more than 10 different
depending on which part of the server you'd like to log (LDAP protocol, database, ACI, etc.).
Those are located at the end of the log4j.properties file:
| log4j.logger.jdbm.recman.BaseRecordManager=FATAL
| log4j.logger.org.apache.directory.server.OPERATIONS_LOG=FATAL
| log4j.logger.org.apache.directory.server.OPERATION_TIME=FATAL
| log4j.logger.org.apache.directory.api.CODEC_LOG=FATAL
| log4j.logger.org.apache.directory.server.ACI_LOG=FATAL
| log4j.logger.org.apache.directory.server.PROVIDER_LOG=FATAL
| log4j.logger.org.apache.directory.server.CONSUMER_LOG=FATAL
| log4j.logger.org.apache.directory.CURSOR_LOG=FATAL
| log4j.logger.org.apache.directory.api=FATAL
| log4j.logger.org.apache.directory.server=DEBUG
| log4j.logger.net.sf.ehcache=FATAL
| log4j.logger.org.apache.mina=FATAL

I'll create/update a page in the ApacheDS documentation to make it easier to understand and
have a real reference on how to enable logging for ApacheDS.
                
> Logging Not Working in M14
> --------------------------
>
>                 Key: DIRSERVER-1871
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1871
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0-M14
>         Environment: Linux
>            Reporter: Jonathan Rosenberg
>            Priority: Critical
>
> Changing logging priortiy of root logger does not cause logging.  Here is log4j.priorities

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message