Previous Topic

Next Topic

Book Contents

Book Index

Log properties

The following properties influence the performance of the framework error and exception logs, their display and storage.

System property

Default value

Description

mbs.log.errorlevel

false

If set to true, framework logs are printed in the system output.

mbs.log.file.dir

logs

Should be set to indicate the recording of the log messages on files. Points to the directory which will contain the log files. This property should not be set in a .prs file. Instead, it should be added as a system property option (with the proper prefix) to the VM_ARGS environment variable (see "Environment Variables" coming next).

mbs.log.file.not_inline

false

If set to true, causes the exceptions to be redirected in a separate file.

mbs.log.file.backups

4

Designates the maximum number of archived log files.

mbs.log.file.size

1048576 (1MB)

The size in bytes set as default of the log files.

mbs.log.file.timeThreshold

10000

The time period in milliseconds over which the log entries are flushed to disk.

mbs.log.useEventThread

true

If set to false, the Framework Log will operate in a separate thread. Otherwise, it will run within the thread created for the Event Manager thus having one thread less in the OSGi environment.

mbs.framework.log.level

Specifies the least severe level to log messages with. Possible values can be "d", "i", "w" or "e", respectively for debug, info, warning or error log level. Only messages with severity equal to or greater than the value of this property will be logged. For example, setting "w" will result in logging warning and error log messages. By default, all log messages are saved. This property should not be set in a .prs file. Instead, it should be added as a system property option (with the proper prefix) to the VM_ARGS environment variable (see "Environment Variables" coming next). Note that the framework log messages can be disabled by setting the mbs.framework.log.level property to 0.

mbs.dateformat.timezone

GMT

It allows to set up the log.txt time stamp to different time zones (by default it is on GMT). So for example if we want European Eastern Time "mbs.dateformat.timezone=EET" should be set in the default.prs file.

If any of the above mentioned mbs.log.file.* properties are set at framework startup, the following configuration properties will be ignored when updating the Log Service configuration: backupFileCount, fileLength, logCount, and storeTimeout. This will persist even after framework restarts - to return back to the normal mode, please unset this system properties and start the framework with a clean storage.