Specify Reader Threads for the Universal Messaging Queue
If the logger will use a Universal Messaging queue, in the Number of Readers field, specify the number of reader threads the logger can use to retrieve entries from the queue and write them to the destination. Each reader thread creates a session with the Universal Messaging server at Integration Server start up.
If you have a standalone Integration Server, set the logger to a number greater than 0. If you have a clustered or non-clustered group of Integration Servers, you might be able to improve performance by designating only one or a few loggers of each type across the cluster or group as readers. In this case, set non-reader loggers to 0, and reader loggers to a number greater than 0.
If the number of reader threads you specify is insufficient, the queue will fill up and the logger will write subsequent entries to the FailedAudit_yyymmdd_hhmmss.log file.
Note: The Number of Readers field does not apply to the messaging audit logger because the messaging audit logger cannot be configured to use a Universal Messaging queue as the audit logging queue. The messaging audit logger always uses the internal queue as the audit logging queue.