Salesforce

How to configure rolling log files for AppServer, WebSpeed and client logs ?

« Go Back

Information

 
TitleHow to configure rolling log files for AppServer, WebSpeed and client logs ?
URL NameP114988
Article Number000169047
EnvironmentProduct: OpenEdge
Version: 10.x,11.x
OS: All supported platforms
Question/Problem Description
How to specify the maximum file size of log files?
How to specify the maximum number of log files?
What are the -logthreshold -numlogfiles startup parameters?
Can UBroker log filesize be limited?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
OpenEdge implements a logging infrastucture that can be used to configure rolling log files, and limit the disk space used. This is facilitated by setting the maximum size of a log file and a maximum number of logfiles to keep, for the AppServer, WebSpeed & ABL client logging.

Specifying the maximum size of the logs (log threshold):
  • For ABL clients (prowin, prowin32, _progres), use the -logthreshold startup parameter
  • For AppServer & WebSpeed, use the brkrLogThreshold (Broker log file threshold size) and srvrLogThreshold (Server log file threshold size) properties for the for the .broker.log and .server.log respectively. These are found the ubroker.properties file, or in the logging settings page of the OpenEdge Explorer.
Where Valid Maximum logfile values are:
  • 0 (default). This means the rolling logs are disabled. There will be a single file, which will grow until an OS limit is hit.
  • Between 500,000 and 2,147,483,647. Values are in bytes (one byte typically holds one character). A file size of up to 2GB, but not lower than 500,000 bytes.  When an out of range value is used, a run-time error occurs and the OpenEdge process terminates.
When the current log file becomes equal or greater than the specified, OpenEdge closes the log and creates a new one. The log file names are based on a sequence number using the following format:  <filename>.999999.<extension> The server log size may grow outside the size specified due to favoring performance of current operations over strict filesize restrictions. For further information, refer to Article  What is the algorithm behind the Unified Broker writing to the server log files when multiple log files are defined?   

Specifying number of logfiles to keep
  • For ABL clients (prowin, prowin32, _progres), use the -numlogfiles startup parameter
  • For AppServer & WebSpeed, use the brkrNumLogFiles (Maximum number of broker log files) and srvrNumLogFiles (Maximum number of server log files) properties for the for the .broker.log and .server.log respectively. These are found the ubroker.properties file, or in the logging settings page of the OpenEdge Explorer.

Where Valid log file retention values are:
  • 0. This will keep all the logfiles.  Excess logs will need to be deleted manually.
  • A range between: 2 and 999999. 
Any time a switch to a new log is needed, a check is performed if there are currently more logs than allowed. When there are, previous logs are deleted based on the sequence number.
For Example: The default number of log files to keep is 3. This means that up to 2 previous files and the current log file will be kept. 

 

Workaround
Notes
References to Written Documentation:

OpenEdge Deployment: Startup Command and Parameter Reference
OpenEdge Development: Debugging and Troubleshooting, section "Log size threshold"

Progress Articles:

Agents managed through Progress Explorer fails to start with error (11065)   

(11064) warning when starting appserver   
 
Keyword Phrase
Last Modified Date7/11/2022 8:16 PM

Powered by