HP Integrity NonStop H-Series - Manual (Page 74)

The file to which boot messages are written can be controlled by the system property
org.jboss.boot.log.file
. The following table shows the system property values for the host
controller and server instances.
System Properties
/ domain/servers/nsasj-server/log/server.log Server instances
/ domain/log/host-controller.log Host Controller
Logging subsystem configuration in domain.xml
The logging subsystem follows the schema defined in jboss-as-logging_1_1.xsd. The schema
file is located in /docs/schema folder.
Log levels
Log levels indicate the criticality of a log message. The level of a particular message is indicated
by the application developer. Each logging framework can have a different way to indicate the
log level of a message. For example, the Java SE Logging framework provides a class by name
java.util.logging.Level
which can be used to indicate the level and provides a method
with signature Logger.log(Level leve, String msg)which can be used to log message
with a particular severity. Log levels are used by log categories and handlers to limit the messages
they handle. They handle log messages that are either equal to or more severe than the level they
are set. The following are the log levels:
Description Level
Use to indicate events that can cause critical service failure and application shutdown,
and possibly cause NSASJ to shutdown. FATAL
Use to indicate an error that has occurred that can prevent the current activity or request
from completing but does not prevent the application from running. ERROR
Use to indicate a situation that is not in error, but is not considered ideal. May indicate
circumstances that may lead to errors in the future. WARN
Use for messages that indicate the overall progress of the application. Often used for
application startup, shutdown and other major lifecycle events. INFO
Use for messages that indicate the progress of individual requests or activities of an
application. Log messages of DEBUG are usually captured when debugging an application. DEBUG
Use for messages that provide detailed information about the running state of an
application. Log messages of TRACE are usually captured when debugging an application. TRACE
Log category
Each logger is identified by a name which is also known as log category. A category is the
same as the Java package. All classes in that Java package and its sub packages are all assigned
the logger. A category that is the closest match to the package of a particular class is assigned as
the logger for that class. For example, if there are two loggers with names com.hp and
com.hp.samples
, then the logger for the class com.hp.samples.simple.HelloWorld is
the latter and the logger for the class com.hp.Tools is the former. Each logger can define a
set of handlers to publish messages. If a logger does not defines its own handler, then the handlers
defined for the root logger are used.
Root logger
The root logger is assigned if no other logger is found.
74 Configuring NSASJ