Logging for the Legacy ActiveSpaces Cluster

You must configure logging for the Legacy ActiveSpaces Cluster in TIBCO BusinessEvents separately. To do so, set the properties in the CDD file.

Properties in the CDD File

Property Description
be.engine.cluster.as.log.dir The directory to which the Legacy ActiveSpaces log files will be written. If unspecified, the logs will be written to the same directory as the TIBCO BusinessEvents logs.
be.engine.cluster.as.log.filename File name of the log file.

By default, the file name is <engineName>-as.log.

be.engine.cluster.as.log.level The log level specifying how much logging is to be filtered out. See Configuration Levels for the Legacy ActiveSpaces Cluster Logging for details.

By default, the log level is set to INFO.

be.engine.cluster.as.logfile.count Specifies the number of rolling log files allowed. Count is specified in integer.
be.engine.cluster.as.logfile.size Log files are rolled over to a new log file when the specified size limit is reached. Size is specified in bytes.
be.engine.cluster.as.logfile.append Set to true/false, specifies whether to append the logs to new files.

Configuration Levels for the Legacy ActiveSpaces Cluster Logging

Following levels can be used to specify the level of logging for the Legacy ActiveSpaces cluster logs. Note that the logging levels are case insensitive.

Level Description
None Highest possible rank. Filters out all logging messages (turns logging off for the specified module).
Fatal Logs only severe runtime errors that cause the application to stop running.
Error Also logs runtime errors that might not cause the application to stop running.
Warn Also logs potentially harmful runtime events or situations.
Info Also logs runtime informational events of general interest.
Fine Also logs detailed runtime informational events, for use in identifying issues.
Finer Also logs even more detailed runtime information.
Finest Lowest possible rank. Turns on all logging including any custom logging levels.