E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (8)
View Page History
...
{section} h1. Logging systems
Petals ESB Hazelcast Registry uses the logging system provided by the JDK.
The logger configuration is determined according to the following ordered rules:
...{section}
h1. Petals ESB Hazelcast Registry Logging specificities
h2. Default levels
...h2. Petals formatter
The Petals formatter {{org.ow2.petals.log.formatter.LogDataFormatter}} is used for traces of the Petals ESB Hazelcast Registry node. The format of the logged message is :
{panel:borderStyle=solid}+YYYY/MM/DD+ +HH:MM:SS,FFF+ +GMT+ +LOG LEVEL+ \[+LOGGER NAME+] : +LOG MESSAGE+{panel}
...h1. Tuning your logging configuration
h2. Petals ESB Hazelcast Registry node starts automatically on Debian-based system
If your Petals ESB Hazelcast Registry nodes used in production are:
* installed on Debian-based systems through Debian packages,
* and, running in [automatic mode|Starting and stopping Petals ESB Hazelcast Registry installed by Debian packages],
you can disable the log handler 'console' for which all generated traces on the standard output are discarded, and used only a log handler 'file' ({{java.util.logging.FileHandler}}, {{org.ow2.petals.log.handler.PetalsFileHandler}} according to your needs.
...{code}
h2. Petals ESB Hazelcast Registry node starts manually or installed through ZIP archive
If your Petals ESB Hazelcast Registry installation does not satisfy the previous criteria (not running in automatic mode on a Debian-based system), you can improve performance decreasing the level of the log handler 'console':
{code}
# Configuration of the handler ConsoleHandler
# Configuration of the handler ConsoleHandler
...