Managing the OSGi log files of JVM servers

The OSGi framework writes errors to a set of log files in the working directory of the JVM server. You can manage the number and size of the log files for each JVM server if the defaults are not appropriate for your environment.

About this task

The OSGi framework writes errors to a log file in the $WORK_DIR/applid/jvmserver/configuration directory on zFS, where $WORK_DIR is the working directory of the JVM server, applid is the CICS APPLID, and jvmserver is the name of the JVMSERVER resource. If you do not set a value for $WORK_DIR in the JVM profile, the logs are output to the z/OS UNIX home directory for the CICS region.

The OSGi framework continues to write to the log file until it reaches 1000 KB in size. After this, the OSGi framework creates another log file to write out further error messages. You can have up to ten log files in the directory. After the tenth log file is full, the OSGi framework writes over the oldest log file. Each JVM server can therefore have up to 10,000 KB of storage allocated to log files in zFS.

You can add options to the JVM profile to change the number and size of log files that are used by the OSGi framework to reduce or increase the number of files and the storage usage.

Procedure

Example

The following example shows a JVM profile with the two parameters specified. In this example, the OSGi framework can use up to five log files and each log file has a maximum size of 500 KB.
#Parameters to control the number and size of OSGi logs  
#
-Declipse.log.backup.max=5
-Declipse.log.size.max=500
#
#


managing_osgi_logs.html | Timestamp icon Last updated: Monday, 5 June 2017