Try OpenEdge Now
skip to main content
Configuration
Configuring WebSpeed Messengers and WebSpeed Transaction Servers : WebSpeed Messenger administration : Configuring a WebSpeed Messenger : WebSpeed Messenger properties : WebSpeed Messenger Logging Setting properties
 
WebSpeed Messenger Logging Setting properties
For complete information about these logging settings, see OpenEdge Development: Debugging and Troubleshooting.
Table 81. WebSpeed Messenger Logging Setting properties
Property
Description
Log filename
Location and name of the log file.
Logging level
A value that specifies the amount of information to be written to the Messenger log. Select from the following values in the drop-down list:
*None — Log no entries. This is equivalent to turning logging off.
*Error Only — Log OpenEdge error messages. This includes all error messages and is unrelated to the entry types specified. Errors continue to be logged at all higher levels.
*Basic — Logging entry types determine the logged information. Each entry type generates at least some output. This is the default.
*Verbose — Logging entry types determine the logged information, but it is typically more information than Basic.
*Extended — Logging entry types determine the logged information, but it is typically more information than Verbose.
Logging entry types
The one valid entry type for WebSpeed Messenger logging is MsgrTrace, which turns on logging for WebSpeed Messengers. The information logged depends on which Messenger is running and the logging level specified. For example:
*Basic — For CGIIP, logs the start and end of the request, and the values of the CONTENT_LENGTH, PATH_INFO and QUERY_STRING variables. For other Messengers, logs the environment variables.
*Verbose — Same as Basic but also includes the CGIIP environment variables and the environment variables in binary format for other Messengers.
*Extended — Same as Verbose, but also includes the environment variables in binary format for CGIIP.
You can specify a logging level on the entry type. For example: MsgrTrace:3
Log file threshold size
A value of 0 or a value between 500,000 and 2,147,483,647, where 0 means there is no limit on the log file size other than what the operating system imposes.
Maximum number of log files
The number of rolled-over log files to keep. The value can be 0 or a value between 2 and 999999, where 0 means there is no limit on the number of server log files to keep. The specified number represents the maximum total number of log files to keep on disk at any time, including the current log file being written to.
When the file becomes equal to or greater than the Log file threshold size, the client process renames it and creates a new log file. The file is renamed as follows, where ###### is a number starting at 000001 and increasing to 999999, after which it rolls back over to 000001:
filename.######.extension