directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r870981 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/5.3-logs.html
Date Wed, 24 Jul 2013 12:45:14 GMT
Author: buildbot
Date: Wed Jul 24 12:45:14 2013
New Revision: 870981

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 24 12:45:14 2013
@@ -1 +1 @@
-1506458
+1506529

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html Wed Jul 24
12:45:14 2013
@@ -158,42 +158,34 @@
 #    See the License for the specific language governing permissions and
 #    limitations under the License.
 #############################################################################
-log4j.rootCategory=WARN, R, stdout
+log4j.rootCategory=WARN, F
 
-log4j.appender.stdout=org.apache.log4j.ConsoleAppender
-log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
-
-log4j.appender.R=org.apache.log4j.RollingFileAppender
-log4j.appender.R.File=${apacheds.log.dir}/apacheds.log
-
-log4j.appender.R.MaxFileSize=1024KB
-# Keep some backup files
-log4j.appender.R.MaxBackupIndex=5
-
-log4j.appender.R.layout=org.apache.log4j.PatternLayout
-log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
-
-log4j.appender.stdout.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
-
-# with these we'll not get innundated when switching to DEBUG
-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=FATAL
-log4j.logger.net.sf.ehcache=FATAL
-log4j.logger.org.apache.mina=FATAL
+log4j.appender.F=org.apache.log4j.RollingFileAppender
+log4j.appender.F.File=${apacheds.log.dir}/apacheds.log
+log4j.appender.F.MaxFileSize=1024KB
+log4j.appender.F.MaxBackupIndex=5
+log4j.appender.F.layout=org.apache.log4j.PatternLayout
+log4j.appender.F.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
+
+# Specific loggers (useful for debugging)
+#log4j.logger.jdbm.recman.BaseRecordManager=DEBUG
+#log4j.logger.org.apache.directory.server.OPERATION_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.OPERATION_TIME=DEBUG
+#log4j.logger.org.apache.directory.api.CODEC_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.ACI_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.PROVIDER_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.CONSUMER_LOG=DEBUG
+#log4j.logger.org.apache.directory.CURSOR_LOG=DEBUG
+#log4j.logger.org.apache.directory.api=DEBUG
+#log4j.logger.org.apache.directory.server=DEBUG
+#log4j.logger.net.sf.ehcache=DEBUG
+#log4j.logger.org.apache.mina=DEBUG
 </pre></div>
 
 
 <h2 id="532-default-log-level">5.3.2 Default log level</h2>
 <p>By default, ApacheDS ships with a default log level set to <strong>WARN</strong>
as indicated in the first line of the <em><strong>log4j.properties</strong></em>
file:</p>
-<div class="codehilite"><pre>log4j.rootCategory=WARN, R, stdout
+<div class="codehilite"><pre>log4j.rootCategory=WARN, F
 </pre></div>
 
 
@@ -202,42 +194,119 @@ log4j.logger.org.apache.mina=FATAL
 <thead>
 <tr>
 <th align="center">Level</th>
-<th>Usage</th>
+<th>Description</th>
 </tr>
 </thead>
 <tbody>
 <tr>
 <td align="center"><em><strong>OFF</strong></em></td>
-<td>The <em>OFF</em> has the highest possible rank and is intended to turn
off logging.</td>
+<td>Highest possible rank and is intended to turn off logging.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>FATAL</strong></em></td>
-<td>The <em>FATAL</em> level designates very severe error events that will
presumably lead the application to abort.</td>
+<td>Very severe error events that will presumably lead the application to abort.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>ERROR</strong></em></td>
-<td>The <em>ERROR</em> level designates error events that might still allow
the application to continue running.</td>
+<td>Error events that might still allow the application to continue running.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>WARN</strong></em></td>
-<td>The <em>WARN</em> level designates potentially harmful situations.</td>
+<td>Potentially harmful situations.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>INFO</strong></em></td>
-<td>The <em>INFO</em> level designates informational messages that highlight
the progress of the application at coarse-grained level.</td>
+<td>Informational messages that highlight the progress of the application at coarse-grained
level.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>DEBUG</strong></em></td>
-<td>The <em>DEBUG</em> Level designates fine-grained informational events
that are most useful to debug an application.</td>
+<td>Fine-grained informational events that are most useful to debug an application.</td>
 </tr>
 <tr>
 <td align="center"><em><strong>TRACE</strong></em></td>
-<td>The <em>TRACE</em> Level designates finer-grained informational events
than the DEBUG.</td>
+<td>Finer-grained informational events than the DEBUG.</td>
 </tr>
 </tbody>
 </table>
 <p>Please refer to the <a href="http://logging.apache.org/log4j/1.2/manual.html"><strong>Log4J
Manual</strong></a> for more details.</p>
 <h2 id="532-apacheds-specific-loggers">5.3.2 ApacheDS specific loggers</h2>
+<p>Bundled at the end of the <em><strong>log4j.properties</strong></em>
file, are a set of specific loggers dedicated to a particular kind of events:</p>
+<div class="codehilite"><pre># Specific loggers (useful for debugging)
+#log4j.logger.jdbm.recman.BaseRecordManager=DEBUG
+#log4j.logger.org.apache.directory.server.OPERATION_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.OPERATION_TIME=DEBUG
+#log4j.logger.org.apache.directory.api.CODEC_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.ACI_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.PROVIDER_LOG=DEBUG
+#log4j.logger.org.apache.directory.server.CONSUMER_LOG=DEBUG
+#log4j.logger.org.apache.directory.CURSOR_LOG=DEBUG
+#log4j.logger.org.apache.directory.api=DEBUG
+#log4j.logger.org.apache.directory.server=DEBUG
+#log4j.logger.net.sf.ehcache=DEBUG
+#log4j.logger.org.apache.mina=DEBUG
+</pre></div>
+
+
+<p>The table below summarizes what each specific logger does:</p>
+<table>
+<thead>
+<tr>
+<th>Logger</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>log4j.logger.<strong>jdbm.recman.BaseRecordManager</strong></td>
+<td>Logs all information related to the JDBM database used to store the entries.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server.OPERATION_LOG</strong></td>
+<td>Logs all executed operations (search, add, delete, etc.).</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server.OPERATION_TIME</strong></td>
+<td>Logs the time each operation takes to execute.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.api.CODEC_LOG</strong></td>
+<td>Logs all incoming and outgoing LDAP Protocol requests/responses.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server.ACI_LOG</strong></td>
+<td>Logs all information related to the ACI system.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server.PROVIDER_LOG</strong></td>
+<td>Logs all information related to the Replication Provider(s).</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server.CONSUMER_LOG</strong></td>
+<td>Logs all information related to the Replication Consumer(s).</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.CURSOR_LOG</strong></td>
+<td>Logs all information related to the Cursors handling the search of entries in the
database.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.api</strong></td>
+<td>A general logger which logs all classes of the Apache Directory LDAP API.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.directory.server</strong></td>
+<td>A general logger which logs all classes of ApacheDS.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>net.sf.ehcache</strong></td>
+<td>A general logger which logs all classes of the Ehcache API.</td>
+</tr>
+<tr>
+<td>log4j.logger.<strong>org.apache.mina</strong></td>
+<td>A general logger which logs all classes of the Apache Mina API.</td>
+</tr>
+</tbody>
+</table>
+<p>These loggers are deactivated by default to prevent them interfering with the root
log level. Make sure to uncomment those you would like to activate (by removing the '<em>#</em>'
character in front of the line) and set the dedicated log level according to the kind of information
you're looking for.</p>
 
 
     <div class="nav">



Mime
View raw message