Author: carnold
Date: Fri Aug  8 07:15:55 2008
New Revision: 683970

URL: http://svn.apache.org/viewvc?rev=683970&view=rev
Log:
Bug 43313: Update FAQ

Modified:
    logging/log4j/trunk/src/site/fml/faq.fml

Modified: logging/log4j/trunk/src/site/fml/faq.fml
URL: 
http://svn.apache.org/viewvc/logging/log4j/trunk/src/site/fml/faq.fml?rev=683970&r1=683969&r2=683970&view=diff
==============================================================================
--- logging/log4j/trunk/src/site/fml/faq.fml (original)
+++ logging/log4j/trunk/src/site/fml/faq.fml Fri Aug  8 07:15:55 2008
@@ -73,9 +73,8 @@
 
     <faq id="1.3"><question>What are the prerequisites for log4j?</question>
       <answer>
-         <p>Log4j versions upto and including 1.2.8 are
-         compatible with JDK 1.1.x and later.  Log4j version 1.3 will
-         be compatilble with JDK 1.2 and later.
+         <p>Log4j 1.2.8 and earlier are compatible with JDK 1.1.x and later, 
later versions
+          of log4j 1.2 are compatible with JDK 1.2 and later.
          </p>
 
          <p>The DOMConfigurator is based on the DOM Level 1
@@ -132,7 +131,7 @@
          remote Unix Syslog daemon, to a remote listener using JMS,
          to the NT EventLog or even send e-mail.  </p>
 
-         <p>log4j uses 5 levels, namely DEBUG, INFO, WARN, ERROR and
+         <p>log4j uses 6 levels, namely TRACE, DEBUG, INFO, WARN, ERROR and
          FATAL.
          </p>
 
@@ -299,8 +298,12 @@
      l.debug("Entry number: " + i + " is " + String.valueOf(entry[i]));
    }
        </pre>
+    <p>or using LogMF from the extras companion write</p>
+    <pre class="source">
+    LogMF.debug("Entry number: {0} is {1}", i, entry[i]);
+    </pre>
 
-       <p>This way you will not incur the cost of parameter
+    <p>This way you will not incur the cost of parameter
        construction if debugging is disabled for logger
        <code>l</code>. On the other hand, if the logger is debug
        enabled, you will incur the cost of evaluating whether the
@@ -577,8 +580,10 @@
        or creating the logfile.  Note that because the clocks of
        various machines may not be synchronized, there may be
        timestamp inconsistencies between events generated on
-       different hosts.
-       </p>
+       different hosts.  The EnhancedPatternLayout in the extras companion
+    supports explicit specification of the timezone using a pattern like
+    "%d{HH:mm}{GMT}".
+    </p>
     </answer></faq>
 
              <faq id="3.5"><question>Why can't log4j find my properties file 
in a J2EE or WAR
@@ -823,5 +828,16 @@
              </p>
           </answer>
       </faq>
+      <faq id="rfa">
+          <question>Why isn't my rolling file appender properly rolling files 
or why does
+              logging events get written to the old log file?</question>
+          <answer>Most commonly this is due to multiple appenders attempting to
+          use the same file path and most likely by having multiple 
independent 
+          instances of log4j read the same configuration file, however having 
the log file
+          open by another process (an editor, backup utility) can also 
interfere with rolling.
+          No provided file appender is reliable when multiple instances are 
writing to
+          the same file path and java.io provides no mechanism to coordinate 
writing
+          between JVM's.</answer>
+      </faq>
   </part>
 </faqs>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to