Changing System Logging
Sterling B2B Integrator writes various types of messages to the log files on disk. The default is to log only the errors.
If your system logging level is set to ALL, you may find that you do not require all the logging messages that are collected because of resource limitations.
If your system logging level is set to ERROR, you may find that you require additional messages from more detailed logging.
For information about system logs and how to change system logging levels, refer to the topic Managing System Logs.
Enabling Async Logging (V5.2.6 or later)
Prior to V5.2.6, threads could only be written to a log entry serially. Writing log entries asynchronously, leaving a dedicated thread to perform all the writing in batches, is a more efficient logging method, and can improve performance by executing I/O operations on a separate thread.
By default, flogger and systemlogger are set as async loggers. If you want to set additional loggers as async, update the log.properties file for each and set the logAsync property to true.
| Parameter | Description |
|---|---|
| <loggername>.logAsync=[false|true] | When logAsync=true, the logger is async, and
logAsyncSize and logAsyncBlocking are
used. When logAsync=false, the logger is not sync - it operates the same as previously. logAsyncSize and logAsyncBlocking have no impact. |
| <loggername>.logAsyncSize=#[value] | LogAsyncSize sets the buffer size. This is the number of messages allowed in the event buffer before the calling thread is blocked (if logAsyncBlocking is true) or until messages are summarized and discarded. Changing the size will not affect messages already in the buffer. Default is 800. |
| <loggername>.logAsyncBlocking=[false|true] | logAsyncBlocking tells the appender to wait if there is no space available in the event buffer (true) or immediately return (false). Default is true. |