Questions et reponses d'entretien

Logging helps in debugging as well. Although debuggers are available but frankly it takes time to debug an application using a debugger. An application can be debugged more easily with few well-placed logging messages. So we can safely say that logging is a very good debugging tool. If logging is done sensibly and wisely, it can provide detailed context for application failures.
In distributed applications (e.g. web/remote applications), the logging is very important. The administrator can read logs to learn about the problems that occurred during some interval.
Java's built-in APIs provide logging options but they are not that flexible. Another option is to use Apache's open source logging framework called log4j. 

Drawbacks of logging applications:
There are some drawbacks of use logging in your application. For example: logging will
- pollute the code
- increase the size of the code
- reduce the speed

These are important points because, we ultimately want efficient applications. Log4J has the solution to this. You may turn on or turn off the logging at runtime by changing the configuration file. This means no change in the Java source code (binary).

• loggers
• appenders
• layouts

• Apache log4j is an open-source and due to this, it's completely free to use.
• You can easily save log information into either files or even databases.
• Can be used for projects of any size small, medium, or large.

The following are features of log4j:

• Log4j 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 a fail-stop. However, although it certainly strives to ensure delivery, log4j does not guarantee that each log statement will be delivered to its destination.

The two static methods in log4j for obtaining a logger object are:

• public static Logger getRootLogger()
• public static Logger getLogger(String name)

Log4j file is defined by the name log4j.properties, it keeps properties in key-value pairs. By default, the log manager looks for a file name log4j.properties in the CLASSPATH.

Package level logging is the standard logging of log4j, with this we would determine the package and the associated level.

Following are the Pros and Cons of Logging:

• Logging is an important component of 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 use.

The DEBUG log level designates fine-grained informational events that are most useful to debug an application.

The ERROR log level designates error events that might still allow the application to continue running.

The FATAL log level designates very severe error events that will presumably lead the application to abort.

The INFO log level designates informational messages that highlight the progress of the application at a coarse-grained level.

The OFF log level is the highest possible rank and is intended to turn off logging.

The TRACE log level designates finer-grained informational events than the DEBUG.

The WARN log level designates potentially harmful situations.

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.

For example: if the log level is mentioned as 'WARN' in the log4j properties. Then the logs will be coming in the log file are: WARN, ERROR, FATAL

The following syntax defines the root logger with WARN mode turning DEBUG mode off.

# Define the root logger with appender file

log = /usr/home/log4j log4j.rootLogger = WARN, FILE