log4j layouts

Using layouts.

Information
To customize the output format of the print messages a layout must be associated to an appender. There are serveral layouts you can choose:

• ObjectRenderer.
  The ObjectRenderer render objects as strings.
  
  
• PatternLayout.
  The PatternLayout lets you specify the output format according to conversion patterns similar to the C language printf function. A conversion pattern is composed of literal text and format control expressions called conversion specifiers. Each conversion specifier starts with a percent sign (%) and is followed by optional format modifiers and a conversion character. The conversion character specifies the type of data, e.g. category, priority, date, thread name. The format modifiers control such things as field width, padding, left and right justification. Here below serveral examples:
  
  log4j.appender.stdout.layout.ConversionPattern=%-5p [%t]: %m%n
  ERROR [http-8080-Processor5]: This is my error message.
  
  log4j.appender.stdout.layout.ConversionPattern=%d [%c{1}] %p - %m%n
  2005-03-26 13:00:54,654 [DemoAction] ERROR - This is my error message.
  
  log4j.appender.stdout.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} %-5p [%c] - %m%n
  26 mrt 2005 13:06:36 ERROR [com.mobilefish.DemoAction] - This is my error message.
  
  log4j.appender.stdout.layout.ConversionPattern=%5p [%C:%M] (%F:%L) - %m%n
  ERROR [com.mobilefish.DemoAction:execute] (DemoAction.java:68) - This is my error message.
  
  log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %r %5p (%l) - %m%n
  13:38:42,976 10 ERROR (com.mobilefish.DemoAction.execute(DemoAction.java:69)) - This is my error message.
  
  
  An overview of conversion characters:
  
  Conversion CharacterEffectcUsed to output the category of the logging event.
  The category conversion specifier can be optionally followed by precision specifier, that is a decimal constant in brackets.
  
  If a precision specifier is given, then only the corresponding number of right most components of the category name will be printed.
  By default the category name is printed in full.
  
  For example, for the category name "a.b.c" the pattern %c{2} will output "b.c".CUsed to output the fully qualified class name of the caller issuing the logging request. This conversion specifier can be optionally followed by precision specifier, that is a decimal constant in brackets.
  
  If a precision specifier is given, then only the corresponding number of right most components of the class name will be printed.
  By default the class name is output in fully qualified form.
  
  For example, for the class name "org.apache.xyz.SomeClass", the pattern %C{1} will output "SomeClass".
  
  WARNING. Generating the caller class information is slow. Thus, it's use should be avoided unless execution speed is not an issue.dUsed to output the date of the logging event. The date conversion specifier may be followed by a date format specifier enclosed between braces. For example,%d{HH:mm:ss,SSS} or %d{dd MMM yyyy HH:mm:ss,SSS}. If no date format specifier is given then ISO8601 format is assumed.
  
  The date format specifier admits the same syntax as the time pattern string of the java.text.SimpleDateFormat. Although part of the standard JDK, the performance of SimpleDateFormat is quite poor.
  
  For better results it is recommended to use the log4j date formatters. These can be specified using one of the strings "ABSOLUTE", "DATE" and "ISO8601" for specifying AbsoluteTimeDateFormat, DateTimeDateFormat and respectively ISO8601DateFormat. For example, %d{ISO8601} or %d{ABSOLUTE}.
  
  These dedicated date formatters perform significantly better than SimpleDateFormat.FUsed to output the file name where the logging request was issued.
  
  WARNING. Generating caller location information is extremely slow.
  It's use should be avoided unless execution speed is not an issue.lUsed to output location information of the caller which generated the logging event.
  
  The location information depends on the JVM implementation but usually consists of the fully qualified name of the calling method followed by the callers source the file name and line number between parentheses.
  
  The location information can be very useful. However, it's generation is extremely slow. It's use should be avoided unless execution speed is not an issue.LUsed to output the line number from where the logging request was issued.
  
  WARNING. Generating caller location information is extremely slow. It's use should be avoided unless execution speed is not an issue.mUsed to output the application supplied message associated with the logging event.
  MUsed to output the method name where the logging request was issued.
  
  WARNING. Generating caller location information is extremely slow. It's use should be avoided unless execution speed is not an issue.nOutputs the platform dependent line separator character or characters.
  
  This conversion character offers practically the same performance as using non-portable line separator strings such as "\n", or "\r\n".
  Thus, it is the preferred way of specifying a line separator.pUsed to output the priority of the logging event.rUsed to output the number of milliseconds elapsed since the start of the application until the creation of the logging event.tUsed to output the name of the thread that generated the logging event.xUsed to output the NDC (nested diagnostic context) associated with the thread that generated the logging event.XUsed to output the MDC (mapped diagnostic context) associated with the thread that generated the logging event. The X conversion character must be followed by the key for the map placed between braces, as in %X{clientNumber} where clientNumber is the key. The value in the MDC corresponding to the key will be output.%The sequence %% outputs a single percent sign.
  
  An overview of format modifiers:
  
  Format modifierleft justifyminimum widthmaximum widthcomment%20cfalse20noneLeft pad with spaces if the category name is less than 20 characters long.%-20ctrue20noneRight pad with spaces if the category name is less than 20 characters long.%.30cNAnone30Truncate from the beginning if the category name is longer than 30 characters.%20.30cfalse2030Left pad with spaces if the category name is shorter than 20 characters. However, if category name is longer than 30 characters, then truncate from the beginning.%-20.30ctrue2030Right pad with spaces if the category name is shorter than 20 characters. However, if category name is longer than 30 characters, then truncate from the beginning.