IBM Support

Tivoli Access Manager Java Runtime JLog file rollover

Question & Answer


Question

When "baseGroup.PDJTraceLogger.isLogging=true" in the PDJLog.properties file, the Tivoli Access Manager (TAM) Java Runtime will log trace information. How does this rollover mechanism work?

Answer

When the JLog starts logging, it will start logging in file "1"....for example


<pd-home>/log/trace__amj1.log (windows)
or
<var-dir>/PolicyDirector/log/trace__amj1.log (unix)

When this file fills up, this file will be renamed to trace__amj2.log, and the writing will continue in a new trace__amj1.log.

When this file fills up, trace__amj2.log will be renamed to trace__amj3.log, trace__amj1.log will be renamed to trace__amj2.log, and the logging continues in trace__amj1.log.

As such, the higher the number the file, the older it is.

This process will continue until you reach the maximum number of files as configured in "baseGroup.PDJTraceFileHandler.maxFiles". Once this max is reached, the oldest log file is discarded.
[{"Product":{"code":"SSPREK","label":"Tivoli Access Manager for e-business"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java Runtime","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1;6.0;6.1;6.1.1;7.0","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

More support for:
Tivoli Access Manager for e-business

Software version:
5.1, 6.0, 6.1, 6.1.1, 7.0

Document number:
346953

Modified date:
16 June 2018

UID

swg21231876

Manage My Notification Subscriptions