Logging, Configuration, Default container configuration – HP Integrity NonStop H-Series User Manual
Page 73
Table 22 Elements of transaction subsystem (continued)
Description
Attributes
NOTE:
In this release of NSASJ each instance runs a recovery manager and
a status manager. In future releases there will be one instance of recovery
manager that will query the status manager on each NSASJ instance and
perform the recovery operation.
The following are the attributes defined in this element:
coordinator-environment
•
default-timeout
: Specifies the default transaction timeout in seconds.
•
enable-statistics
: Specifies whether to enable transaction statistics.
By default this is false.
•
enable-tsm-statistics
: Specifies whether to enable transaction
status manager statistics. By default this is false.
Logging
NSASJ provides a flexible and configurable logging infrastructure that is used by the container,
and also available for use by all applications deployed in the container. The following lists some
exclusive features of the NSASJ logging infrastructure (inherited from JBoss):
•
The logging infrastructure is based on JBoss LogManager and can support several third party
logging frameworks such as JBoss Logging, Java SE Logging (java.util.logging) and
Apache log4j.
•
The logging infrastructure is integrated with EMS. Thus, enabling log messages to be published
to EMS.
•
The logging infrastructure supports logging configuration for each and every application.
•
The log file rollover can either be time based or size based.
•
The logging configuration can be modified at run time using management tools.
Configuration
The NSASJ logging infrastructure is used by the container itself and can also be used by the
applications deployed in the container. The container uses JBoss Logging, whereas, the framework
applications are free to use JBoss Logging, Java SE Logging or Apache log4j as their logging
frameworks. The discussions in the subsequent subsections explain the following:
•
The configuration that is used by the container.
•
The way applications need to be configured to use logging infrastructure with different logging
frameworks.
•
The details about the configuration file.
Default container configuration
The default logging infrastructure comes with two configurations. First is the one that is used while
booting the container, and the other is the one that is used once the container is booted and the
logging subsystem is configured. The first configuration is usually referred as boot logging
configuration. Boot logging is configured in the file
The logging subsystem
defined in domain.xml overrides the boot logging configuration. The boot logging configuration
is a properties file. The format of keys and their values are as defined by the JBoss Logging
framework.
Logging
73