Category: log4j

log4j – Installation ”; Previous Next log4j API package is distributed under the Apache Software License, a full-fledged open source license certified by the open source initiative. The latest log4j version, including full-source code, class files and documentation can be found at http://logging.apache.org/log4j/. To install log4j on your system, download apache-log4j-x.x.x.tar.gz from the specified URL and follow the steps give below. Step 1 Unzip and untar the downloaded file in /usr/local/ directory as follows: $ gunzip apache-log4j-1.2.15.tar.gz $ tar -xvf apache-log4j-1.2.15.tar apache-log4j-1.2.15/tests/input/ apache-log4j-1.2.15/tests/input/xml/ apache-log4j-1.2.15/tests/src/ apache-log4j-1.2.15/tests/src/java/ apache-log4j-1.2.15/tests/src/java/org/ ………………………………… While untarring, it would create a directory hierarchy with a name apache-log4j-x.x.x as follows: -rw-r–r– 1 root root 3565 2007-08-25 00:09 BUILD-INFO.txt -rw-r–r– 1 root root 2607 2007-08-25 00:09 build.properties.sample -rw-r–r– 1 root root 32619 2007-08-25 00:09 build.xml drwxr-xr-x 14 root root 4096 2010-02-04 14:09 contribs drwxr-xr-x 5 root root 4096 2010-02-04 14:09 examples -rw-r–r– 1 root root 2752 2007-08-25 00:09 INSTALL -rw-r–r– 1 root root 4787 2007-08-25 00:09 KEYS -rw-r–r– 1 root root 11366 2007-08-25 00:09 LICENSE -rw-r–r– 1 root root 391834 2007-08-25 00:29 log4j-1.2.15.jar -rw-r–r– 1 root root 160 2007-08-25 00:09 NOTICE -rwxr-xr-x 1 root root 10240 2007-08-25 00:27 NTEventLogAppender.dll -rw-r–r– 1 root root 17780 2007-08-25 00:09 pom.xml drwxr-xr-x 7 root root 4096 2007-08-25 00:13 site drwxr-xr-x 8 root root 4096 2010-02-04 14:08 src drwxr-xr-x 6 root root 4096 2010-02-04 14:09 tests Step 2 This step is optional and depends on what features you are going to use from log4j framework. If you already have following packages installed on your machine then it is fine, otherwise you need to install them to make log4j work. JavaMail API: The e-mail based logging feature in log4j requires the Java Mail API (mail.jar) to be installed on your machine from glassfish.dev. JavaBeans Activation Framework: The Java Mail API will also require that the JavaBeans Activation Framework (activation.jar) be installed on your machine from http://java.sun.com/products/javabeans/jaf/index.jsp. Java Message Service: The JMS-compatible features of log4j will require that both JMS and Java Naming and Directory Interface JNDI be installed on your machine from http://java.sun.com/products/jms. XML Parser: You need a JAXP-compatible XML parser to use log4j. Make sure you have Xerces.jar installed on your machine from http://xerces.apache.org/xerces-j/install.html. Step 3 Now you need to set up the CLASSPATH and PATH variables appropriately. Here we are going to set it just for the log4j.x.x.x.jar file. $ pwd /usr/local/apache-log4j-1.2.15 $ export CLASSPATH=$CLASSPATH:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar $ export PATH=$PATH:/usr/local/apache-log4j-1.2.15/ Print Page Previous Next Advertisements ”;

log4j – Quick Guide ”; Previous Next log4j – Overview log4j is a reliable, fast and flexible logging framework (APIs) written in Java, which is distributed under the Apache Software License. log4j has been ported to the C, C++, C#, Perl, Python, Ruby, and Eiffel languages. log4j is highly configurable through external configuration files at runtime. It views the logging process in terms of levels of priorities and offers mechanisms to direct logging information to a great variety of destinations, such as a database, file, console, UNIX Syslog, etc. log4j has three main components: loggers: Responsible for capturing logging information. appenders: Responsible for publishing logging information to various preferred destinations. layouts: Responsible for formatting logging information in different styles. History of log4j Started in early 1996 as tracing API for the E.U. SEMPER (Secure Electronic Marketplace for Europe) project. After countless enhancements and several incarnations, the initial API has evolved to become log4j, a popular logging package for Java. The package is distributed under the Apache Software License, a full-fledged open source license certified by the open source initiative. The latest log4j version, including its full-source code, class files, and documentation can be found at http://logging.apache.org/log4j/. log4j Features It is thread-safe. It is optimized for speed. It is based on a named logger hierarchy. It supports multiple output appenders per logger. It supports internationalization. It is not restricted to a predefined set of facilities. Logging behavior can be set at runtime using a configuration file. It is designed to handle Java Exceptions from the start. It uses multiple levels, namely ALL, TRACE, DEBUG, INFO, WARN, ERROR and FATAL. The format of the log output can be easily changed by extending the Layout class. The target of the log output as well as the writing strategy can be altered by implementations of the Appender interface. It is fail-stop. However, although it certainly strives to ensure delivery, log4j does not guarantee that each log statement will be delivered to its destination. Pros and Cons of Logging Logging is an important component of the software development. A well-written logging code offers quick debugging, easy maintenance, and structured storage of an application”s runtime information. Logging does have its drawbacks also. It can slow down an application. If too verbose, it can cause scrolling blindness. To alleviate these concerns, log4j is designed to be reliable, fast and extensible. Since logging is rarely the main focus of an application, the log4j API strives to be simple to understand and to use. log4j – Installation log4j API package is distributed under the Apache Software License, a full-fledged open source license certified by the open source initiative. The latest log4j version, including full-source code, class files and documentation can be found at http://logging.apache.org/log4j/. To install log4j on your system, download apache-log4j-x.x.x.tar.gz from the specified URL and follow the steps give below. Step 1 Unzip and untar the downloaded file in /usr/local/ directory as follows: $ gunzip apache-log4j-1.2.15.tar.gz $ tar -xvf apache-log4j-1.2.15.tar apache-log4j-1.2.15/tests/input/ apache-log4j-1.2.15/tests/input/xml/ apache-log4j-1.2.15/tests/src/ apache-log4j-1.2.15/tests/src/java/ apache-log4j-1.2.15/tests/src/java/org/ ………………………………… While untarring, it would create a directory hierarchy with a name apache-log4j-x.x.x as follows: -rw-r–r– 1 root root 3565 2007-08-25 00:09 BUILD-INFO.txt -rw-r–r– 1 root root 2607 2007-08-25 00:09 build.properties.sample -rw-r–r– 1 root root 32619 2007-08-25 00:09 build.xml drwxr-xr-x 14 root root 4096 2010-02-04 14:09 contribs drwxr-xr-x 5 root root 4096 2010-02-04 14:09 examples -rw-r–r– 1 root root 2752 2007-08-25 00:09 INSTALL -rw-r–r– 1 root root 4787 2007-08-25 00:09 KEYS -rw-r–r– 1 root root 11366 2007-08-25 00:09 LICENSE -rw-r–r– 1 root root 391834 2007-08-25 00:29 log4j-1.2.15.jar -rw-r–r– 1 root root 160 2007-08-25 00:09 NOTICE -rwxr-xr-x 1 root root 10240 2007-08-25 00:27 NTEventLogAppender.dll -rw-r–r– 1 root root 17780 2007-08-25 00:09 pom.xml drwxr-xr-x 7 root root 4096 2007-08-25 00:13 site drwxr-xr-x 8 root root 4096 2010-02-04 14:08 src drwxr-xr-x 6 root root 4096 2010-02-04 14:09 tests Step 2 This step is optional and depends on what features you are going to use from log4j framework. If you already have following packages installed on your machine then it is fine, otherwise you need to install them to make log4j work. JavaMail API: The e-mail based logging feature in log4j requires the Java Mail API (mail.jar) to be installed on your machine from glassfish.dev. JavaBeans Activation Framework: The Java Mail API will also require that the JavaBeans Activation Framework (activation.jar) be installed on your machine from http://java.sun.com/products/javabeans/jaf/index.jsp. Java Message Service: The JMS-compatible features of log4j will require that both JMS and Java Naming and Directory Interface JNDI be installed on your machine from http://java.sun.com/products/jms. XML Parser: You need a JAXP-compatible XML parser to use log4j. Make sure you have Xerces.jar installed on your machine from http://xerces.apache.org/xerces-j/install.html. Step 3 Now you need to set up the CLASSPATH and PATH variables appropriately. Here we are going to set it just for the log4j.x.x.x.jar file. $ pwd /usr/local/apache-log4j-1.2.15 $ export CLASSPATH= $CLASSPATH:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar $ export PATH=$PATH:/usr/local/apache-log4j-1.2.15/ log4j – Architecture log4j API follows a layered architecture where each layer provides different objects to perform different tasks. This layered architecture makes the design flexible and easy to extend in future. There are two types of objects available with log4j framework. Core Objects: These are mandatory objects of the framework. They are required to use the framework. Support Objects: These are optional objects of the framework. They support core objects to perform additional but important tasks. Core Objects Core objects include the following types of objects: Logger Object The top-level layer is the Logger which provides the Logger object. The Logger object is responsible for capturing logging information and they are stored in a namespace hierarchy. Layout Object The layout layer provides objects which are used to format logging information in different styles. It provides support to appender objects before publishing logging information. Layout objects play an important role in publishing logging information in a way that is human-readable and reusable. Appender Object This is a lower-level layer which provides Appender objects. The Appender object is responsible for publishing logging information to various preferred destinations such as a

log4j – Overview ”; Previous Next log4j is a reliable, fast and flexible logging framework (APIs) written in Java, which is distributed under the Apache Software License. log4j has been ported to the C, C++, C#, Perl, Python, Ruby, and Eiffel languages. log4j is highly configurable through external configuration files at runtime. It views the logging process in terms of levels of priorities and offers mechanisms to direct logging information to a great variety of destinations, such as a database, file, console, UNIX Syslog, etc. log4j has three main components: loggers: Responsible for capturing logging information. appenders: Responsible for publishing logging information to various preferred destinations. layouts: Responsible for formatting logging information in different styles. History of log4j Started in early 1996 as tracing API for the E.U. SEMPER (Secure Electronic Marketplace for Europe) project. After countless enhancements and several incarnations, the initial API has evolved to become log4j, a popular logging package for Java. The package is distributed under the Apache Software License, a full-fledged open source license certified by the open source initiative. The latest log4j version, including its full-source code, class files, and documentation can be found at http://logging.apache.org/log4j/. log4j Features It is thread-safe. It is optimized for speed. It is based on a named logger hierarchy. It supports multiple output appenders per logger. It supports internationalization. It is not restricted to a predefined set of facilities. Logging behavior can be set at runtime using a configuration file. It is designed to handle Java Exceptions from the start. It uses multiple levels, namely ALL, TRACE, DEBUG, INFO, WARN, ERROR and FATAL. The format of the log output can be easily changed by extending the Layout class. The target of the log output as well as the writing strategy can be altered by implementations of the Appender interface. It is fail-stop. However, although it certainly strives to ensure delivery, log4j does not guarantee that each log statement will be delivered to its destination. Pros and Cons of Logging Logging is an important component of the software development. A well-written logging code offers quick debugging, easy maintenance, and structured storage of an application”s runtime information. Logging does have its drawbacks also. It can slow down an application. If too verbose, it can cause scrolling blindness. To alleviate these concerns, log4j is designed to be reliable, fast and extensible. Since logging is rarely the main focus of an application, the log4j API strives to be simple to understand and to use. Print Page Previous Next Advertisements ”;

log4j – Useful Resources ”; Previous Next The following resources contain additional information on log4j. Please use them to get more in-depth knowledge on this topic. Useful Links on log4j log4j – Official website of log4j, Apache Logging Services Project – Apache log4j. log4j @ Wikipedia – A short tutorial available at wikipedia. Sun”s Site on JDBC – Sun Developer Network giving link on JDBC material. MySQL Connector/J – MySQL Connector/J is the official JDBC driver for MySQL. Useful Books on log4j To enlist your site on this page, please drop an email to [email protected] Print Page Previous Next Advertisements ”;

log4j – Log Formatting ”; Previous Next Apache log4j provides various Layout objects, each of which can format logging data according to various layouts. It is also possible to create a Layout object that formats logging data in an application-specific way. All Layout objects receive a LoggingEvent object from the Appender objects. The Layout objects then retrieve the message argument from the LoggingEvent and apply the appropriate ObjectRenderer to obtain the String representation of the message. The Layout Types The top-level class in the hierarchy is the abstract class org.apache.log4j.Layout. This is the base class for all other Layout classes in the log4j API. The Layout class is defined as abstract within an application, we never use this class directly; instead, we work with its subclasses which are as follows: DateLayout HTMLLayout PatternLayout. SimpleLayout XMLLayout The Layout Methods This class provides a skeleton implementation of all the common operations across all other Layout objects and declares two abstract methods. Sr.No. Methods & Description 1 public abstract boolean ignoresThrowable() It indicates whether the logging information handles any java.lang.Throwable object passed to it as a part of the logging event. If the Layout object handles the Throwable object, then the Layout object does not ignore it, and returns false. 2 public abstract String format(LoggingEvent event) Individual layout subclasses implement this method for layout specific formatting. Apart from these abstract methods, the Layout class provides concrete implementation for the methods listed below: Sr.No. Methods & Description 1 public String getContentType() It returns the content type used by the Layout objects. The base class returns text/plain as the default content type. 2 public String getFooter() It specifies the footer information of the logging message. 3 public String getHeader() It specifies the header information of the logging message. Each subclass can return class-specific information by overriding the concrete implementation of these methods. Print Page Previous Next Advertisements ”;

log4j – Logging in Files ”; Previous Next To write your logging information into a file, you would have to use org.apache.log4j.FileAppender. FileAppender Configuration FileAppender has the following configurable parameters: Property Description immediateFlush This flag is by default set to true, which means the output stream to the file being flushed with each append operation. encoding It is possible to use any character-encoding. By default, it is the platform-specific encoding scheme. threshold The threshold level for this appender. Filename The name of the log file. fileAppend This is by default set to true, which means the logging information being appended to the end of the same file. bufferedIO This flag indicates whether we need buffered writing enabled. By default, it is set to false. bufferSize If buffered I/O is enabled, it indicates the buffer size. By default, it is set to 8kb. Following is a sample configuration file log4j.properties for FileAppender − # Define the root logger with appender file log4j.rootLogger = DEBUG, FILE # Define the file appender log4j.appender.FILE=org.apache.log4j.FileAppender # Set the name of the file log4j.appender.FILE.File=${log}/log.out # Set the immediate flush to true (default) log4j.appender.FILE.ImmediateFlush=true # Set the threshold to debug mode log4j.appender.FILE.Threshold=debug # Set the append to false, overwrite log4j.appender.FILE.Append=false # Define the layout for file appender log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.conversionPattern=%m%n If you wish to have an XML configuration file equivalent to the above log4j.properties file, then here is the content: <?xml version=”1.0″ encoding=”UTF-8″ ?> <!DOCTYPE log4j:configuration SYSTEM “log4j.dtd”> <log4j:configuration> <appender name=”FILE” class=”org.apache.log4j.FileAppender”> <param name=”file” value=”${log}/log.out”/> <param name=”immediateFlush” value=”true”/> <param name=”threshold” value=”debug”/> <param name=”append” value=”false”/> <layout class=”org.apache.log4j.PatternLayout”> <param name=”conversionPattern” value=”%m%n”/> </layout> </appender> <logger name=”log4j.rootLogger” additivity=”false”> <level value=”DEBUG”/> <appender-ref ref=”FILE”/> </logger> </log4j:configuration> You can try log4j – Sample Program with the above configuration. Logging in Multiple Files You may want to write your log messages into multiple files for certain reasons, for example, if the file size reached to a certain threshold. To write your logging information into multiple files, you would have to use org.apache.log4j.RollingFileAppender class which extends the FileAppender class and inherits all its properties. We have the following configurable parameters in addition to the ones mentioned above for FileAppender − Property Description maxFileSize This is the critical size of the file above which the file will be rolled. Default value is 10 MB. maxBackupIndex This property denotes the number of backup files to be created. Default value is 1. Following is a sample configuration file log4j.properties for RollingFileAppender. # Define the root logger with appender file log4j.rootLogger = DEBUG, FILE # Define the file appender log4j.appender.FILE=org.apache.log4j.RollingFileAppender # Set the name of the file log4j.appender.FILE.File=${log}/log.out # Set the immediate flush to true (default) log4j.appender.FILE.ImmediateFlush=true # Set the threshold to debug mode log4j.appender.FILE.Threshold=debug # Set the append to false, should not overwrite log4j.appender.FILE.Append=true # Set the maximum file size before rollover log4j.appender.FILE.MaxFileSize=5MB # Set the the backup index log4j.appender.FILE.MaxBackupIndex=2 # Define the layout for file appender log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.conversionPattern=%m%n If you wish to have an XML configuration file, you can generate the same as mentioned in the initial section and add only additional parameters related to RollingFileAppender. This example configuration demonstrates that the maximum permissible size of each log file is 5 MB. Upon exceeding the maximum size, a new log file will be created. Since maxBackupIndex is defined as 2, once the second log file reaches the maximum size, the first log file will be erased and thereafter, all the logging information will be rolled back to the first log file. You can try log4j – Sample Program with the above configuration. Daily Log File Generation There may be a requirement to generate your log files on a daily basis to keep a clean record of your logging information. To write your logging information into files on a daily basis, you would have to use org.apache.log4j.DailyRollingFileAppender class which extends the FileAppender class and inherits all its properties. There is only one important configurable parameter in addition to the ones mentioned above for FileAppender: Property Description DatePattern This indicates when to roll over the file and the naming convention to be followed. By default, roll over is performed at midnight each day. DatePattern controls the rollover schedule using one of the following patterns: DatePattern Description ”.” yyyy-MM Roll over at the end of each month and at the beginning of the next month. ”.” yyyy-MM-dd Roll over at midnight each day. This is the default value. ”.” yyyy-MM-dd-a Roll over at midday and midnight of each day. ”.” yyyy-MM-dd-HH Roll over at the top of every hour. ”.” yyyy-MM-dd-HH-mm Roll over every minute. ”.” yyyy-ww Roll over on the first day of each week depending upon the locale. Following is a sample configuration file log4j.properties to generate log files rolling over at midday and midnight of each day. # Define the root logger with appender file log4j.rootLogger = DEBUG, FILE # Define the file appender log4j.appender.FILE=org.apache.log4j.DailyRollingFileAppender # Set the name of the file log4j.appender.FILE.File=${log}/log.out # Set the immediate flush to true (default) log4j.appender.FILE.ImmediateFlush=true # Set the threshold to debug mode log4j.appender.FILE.Threshold=debug # Set the append to false, should not overwrite log4j.appender.FILE.Append=true # Set the DatePattern log4j.appender.FILE.DatePattern=”.” yyyy-MM-dd-a # Define the layout for file appender log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.conversionPattern=%m%n If you wish to have an XML configuration file, you can generate the same as mentioned in the initial section and add only additional parameters related to DailyRollingFileAppender. You can try log4j – Sample Program with the above configuration. Print Page Previous Next Advertisements ”;

Discuss Log4J ”; Previous Next log4j is a reliable, fast and flexible logging framework (APIs) written in Java, which is distributed under the Apache Software License. log4j is a popular logging package written in Java. log4j has been ported to the C, C++, C#, Perl, Python, Ruby, and Eiffel languages. Print Page Previous Next Advertisements ”;

log4j Questions and Answers ”; Previous Next log4j Questions and Answers has been designed with a special intention of helping students and professionals preparing for various Certification Exams and Job Interviews. This section provides a useful collection of sample Interview Questions and Multiple Choice Questions (MCQs) and their answers with appropriate explanations. SN Question/Answers Type 1 log4j Interview Questions This section provides a huge collection of log4j Interview Questions with their answers hidden in a box to challenge you to have a go at them before discovering the correct answer. 2 log4j Online Quiz This section provides a great collection of log4j Multiple Choice Questions (MCQs) on a single page along with their correct answers and explanation. If you select the right option, it turns green; else red. 3 log4j Online Test If you are preparing to appear for a Java and log4j related certification exam, then this section is a must for you. This section simulates a real online test along with a given timer which challenges you to complete the test within a given time-frame. Finally you can check your overall test score and how you fared among millions of other candidates who attended this online test. 4 log4j Mock Test This section provides various mock tests that you can download at your local machine and solve offline. Every mock test is supplied with a mock test key to let you verify the final score and grade yourself. Print Page Previous Next Advertisements ”;

log4j – Logging Levels ”; Previous Next The org.apache.log4j.Level levels. You can also define your custom levels by sub-classing the Level class. Level Description ALL All levels including custom levels. DEBUG Designates fine-grained informational events that are most useful to debug an application. INFO Designates informational messages that highlight the progress of the application at coarse-grained level. WARN Designates potentially harmful situations. ERROR Designates error events that might still allow the application to continue running. FATAL Designates very severe error events that will presumably lead the application to abort. OFF The highest possible rank and is intended to turn off logging. TRACE Designates finer-grained informational events than the DEBUG. How do Levels Works? A log request of level p in a logger with level q is enabled if p >= q. This rule is at the heart of log4j. It assumes that levels are ordered. For the standard levels, we have ALL < DEBUG < INFO < WARN < ERROR < FATAL < OFF. The Following example shows how we can filter all our DEBUG and INFO messages. This program uses of logger method setLevel(Level.X) to set a desired logging level: This example would print all the messages except Debug and Info: import org.apache.log4j.*; public class LogClass { private static org.apache.log4j.Logger log = Logger.getLogger(LogClass.class); public static void main(String[] args) { log.setLevel(Level.WARN); log.trace(“Trace Message!”); log.debug(“Debug Message!”); log.info(“Info Message!”); log.warn(“Warn Message!”); log.error(“Error Message!”); log.fatal(“Fatal Message!”); } } When you compile and run the LogClass program, it would generate the following result − Warn Message! Error Message! Fatal Message! Setting Levels using Configuration File log4j provides you configuration file based level setting which sets you free from changing the source code when you want to change the debugging level. Following is an example configuration file which would perform the same task as we did using the log.setLevel(Level.WARN) method in the above example. # Define the root logger with appender file log = /usr/home/log4j log4j.rootLogger = WARN, FILE # Define the file appender log4j.appender.FILE=org.apache.log4j.FileAppender log4j.appender.FILE.File=${log}/log.out # Define the layout for file appender log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.conversionPattern=%m%n Let us now use our following program − import org.apache.log4j.*; public class LogClass { private static org.apache.log4j.Logger log = Logger.getLogger(LogClass.class); public static void main(String[] args) { log.trace(“Trace Message!”); log.debug(“Debug Message!”); log.info(“Info Message!”); log.warn(“Warn Message!”); log.error(“Error Message!”); log.fatal(“Fatal Message!”); } } Now compile and run the above program and you would get following result in /usr/home/log4j/log.out file − Warn Message! Error Message! Fatal Message! Print Page Previous Next Advertisements ”;

log4j – Architecture ”; Previous Next log4j API follows a layered architecture where each layer provides different objects to perform different tasks. This layered architecture makes the design flexible and easy to extend in future. There are two types of objects available with log4j framework. Core Objects: These are mandatory objects of the framework. They are required to use the framework. Support Objects: These are optional objects of the framework. They support core objects to perform additional but important tasks. Core Objects Core objects include the following types of objects − Logger Object The top-level layer is the Logger which provides the Logger object. The Logger object is responsible for capturing logging information and they are stored in a namespace hierarchy. Layout Object The layout layer provides objects which are used to format logging information in different styles. It provides support to appender objects before publishing logging information. Layout objects play an important role in publishing logging information in a way that is human-readable and reusable. Appender Object This is a lower-level layer which provides Appender objects. The Appender object is responsible for publishing logging information to various preferred destinations such as a database, file, console, UNIX Syslog, etc. The following virtual diagram shows the components of a log4J framework: Support Objects There are other important objects in the log4j framework that play a vital role in the logging framework: Level Object The Level object defines the granularity and priority of any logging information. There are seven levels of logging defined within the API: OFF, DEBUG, INFO, ERROR, WARN, FATAL, and ALL. Filter Object The Filter object is used to analyze logging information and make further decisions on whether that information should be logged or not. An Appender objects can have several Filter objects associated with them. If logging information is passed to a particular Appender object, all the Filter objects associated with that Appender need to approve the logging information before it can be published to the attached destination. ObjectRenderer The ObjectRenderer object is specialized in providing a String representation of different objects passed to the logging framework. This object is used by Layout objects to prepare the final logging information. LogManager The LogManager object manages the logging framework. It is responsible for reading the initial configuration parameters from a system-wide configuration file or a configuration class. Print Page Previous Next Advertisements ”;