Overview

The Framework Log maintains logs, which are generated by the framework. By manipulating specific system properties, logs and stack traces of thrown exceptions can be written to one common file or to many different ones. For optimal performance, it is recommended to use writing to one file, since log files are backed up and multiple files will require multiple I/O operations during backup. The default maximum size of files is 1MB. Upon reaching this limit, the file is automatically archived, using the naming convention mentioned below, and the next one is opened.

The current convention dictates that log files will be no more than four, using the following naming pattern:

• The current file is labeled log.txt, the former – log0.txt, etc. and the least recent one – log3.txt.
• Upon a new file entering the Framework Log, the last one is deleted.
• The naming pattern and the number of files can be modified up to the system integrator’s discretion.

Setup

By means of system properties various functionalities of the Framework Log can be configured, such as having the log information directed to the framework console, a log file or a remote device; storing logs and exceptions in a common file or separate files; changing the number and size of the archived log files. See the "Log properties" section in the Setup guide for the list of setup properties of the Framework Log.

By default, the Framework Log is configured to save log information in files in the bin/vms/<vm_name> directory. Use the nofilelog option of the JVM-specific server startup script to disable this storage. Refer to Starting the framework.