Where are the Corticon Server logs? What are the various log level options available to set loglevel parameter in Corticon Server? - Progress Community

Loading

Skip to Main Content

Where are the Corticon Server logs? What are the various log level options available to set loglevel parameter in Corticon Server?

What are the various log level options available to set loglevel parameter in Corticon Server ? What is the significance of each log level?

Aug 15, 2016
Knowledge

Title

Where are the Corticon Server logs? What are the various log level options available to set loglevel parameter in Corticon Server?

URL Name

000042681

Article Number

000165116

Environment

Product: Corticon Server Version: 5.x OS: All supported platforms Database: N/A Browser: N/A Application Server: N/A

Question/Problem Description

Where are the Corticon Server logs?
What are the various log level options available to set loglevel parameter in Corticon Server ?
What is the significance of each log level?
In what format is the Corticon Server log stored.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

For 5.x up to 5.4.x:

The Corticon Server logs will be stored in a file yyyymmdd.log (located in the %CORTICON_HOME%\Log directory) where yyyy is the year, mm is the month and dd is the day. For e.g. 20140729.log.

If %CORTICON_HOME% is not known the path to the log file can be explicitly set by modifying the logpath parameter for the Corticon Server in the CcCommon.properties file (located within the axis/WEB-INF/lib/CcConfig.jar.

The various log levels that can be used to set the loglevel parameter for Corticon Server in the CcCommon.properties file [located within the axis/WEB-INF/lib/CcConfig.jar] are:

1. VIOLATION
Only Exceptions are logged.
Recommended for deployment because it maximizes Corticon Server performance.
This level also logs ERROR and FATAL messages
This is the recommended log level for Normal Operation

2. RULETRACE
Logs performance statistics (e.g., total time for rule execution, percentage of time on each rulesheet etc.) and information on what specific rules were fired (not just evaluated).
This level includes TIMING and WARNING messages plus all the messages at and below VIOLATION level.

This is the recommended log level for Tracing of Rules Fired.
Do not deploy Corticon Server in production with loglevel set to RULETRACE. While log files are smaller than those generated in DEBUG and INFO modes, they still require significant time to write, thereby impacting the Corticon Server's performance.

3.INFO
All messages except debugging messages are logged.
This is the recommended log level for Reporting Defects and Issues

Never deploy Corticon Server in production with loglevel set to INFO: Log files created in this mode may become very large and slow down Corticon Server's performance by orders of magnitude.

4.DEBUG
All messages are logged, including debugging info.This is the highest level of log detail.
This is the recommended log level for Debugging.
It is meant to be used only at the direction of Progress Technical Support.
Never deploy Corticon Server in production with loglevel set to DEBUG. Log files created in this mode may become very large and slow down Corticon Server's performance by orders of magnitude.
5. DIAGNOSTIC (Starting version 5.4)
Logs server performance diagnostic values at a defined interval. In Corticon 5.4, this is the default loglevel specified.

For 5.5 and above:

The Corticon Server logs will be stored in a file named [CORTICON_WORK_DIR]\logs\CcServer.log.
The various log levels that can be used to set the loglevel parameter for Corticon Server in the [CORTICON_WORK_DIR]\brms.properties file are:

1. OFF
Turn off all logging

2. ERROR
Log only errors

3. WARN
Log all errors and warnings

4. INFO
Log all info, warnings and errors

5. DEBUG
Log all debug information and all messages applicable to INFO level

6. TRACE
Equivalent to DEBUG with some tracing logs

7. ALL
Log all messages

A logFiltersAccept property can also be set to allow the inclusion of specified types of information from running services in the logs. When the log level is set to INFO or higher, this property accepts logging of information types that are listed. The logFiltersAccept property can be set to any of the following by using comma-separated values:

1. RULETRACE
Records performance statistics on rules

2. DIAGNOSTIC
Records of service performance diagnostics at a defined interval (default is 30 seconds)

3. TIMING
Records timing events

4. INVOCATION
Records invocation events

5. VIOLATION
Records exceptions

6. INTERNAL
Records internal debug events

7. SYSTEM
Records low-level errors and fatal events

The default logFiltersAccept setting is: DIAGNOSTIC,SYSTEM

Workaround

Notes

References to Other Documentation:
Corticon Server: Integration & Deployment Guide : Using Corticon Server logs
https://documentation.progress.com/output/ua/Corticon/index.html#page/corticon%2Fusing-corticon-server-logs.html%23

Keyword Phrase

Last Modified Date

6/16/2023 4:39 PM

Corticon General Discussions

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Where are the Corticon Server logs? What are the various log level options available to set loglevel parameter in Corticon Server? - Progress Community