Log Rotation Does Not Work For MWA Dispatcher Log (Doc ID 2328634.1)

Last updated on FEBRUARY 24, 2023

Applies to:

Symptoms

The MWA log rotation is not working for the Dispatcher.
When the dispatcher.log reaches the mwa.MaxLogFileSize=10000000, instead of creating a new dispatcher.log, messages are continuing to be written to the original dispatcher.log and at some point (due to OS limitations) no more data can be written to the dispatcher.log which causes the MWA apps to hang.

To prevent this hang of the MWA apps, has has increased the OS limit on the log to 2Gb, then manually clear out the dispatcher log weekly.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

In the mwa.cfg file, set the mwa.MaxLogFileSize=10000000 (or some smaller number for testing)
Start mwa telnet port and mwa dispatcher.
Monitor the dispatcher.log.
 Dispatcher is polling for any new connections amongst the mwa telnet server ports and will see the following messages (along with other normal error, warnings and connections messages) frequently being written to the log
[Mon Sep 19 10:16:55 2016] runRegistrar: retrun from snttaccept for registrar socket
[Mon Sep 19 10:16:55 2016] runRegistrar: before calling snttaccept for registrar socket
[Mon Sep 19 10:16:55 2016] runRegistrar: retrun from snttaccept for registrar socket
[Mon Sep 19 10:16:55 2016] runRegistrar: before calling snttaccept for registrar socket
[Mon Sep 19 10:16:55 2016] runRegistrar: retrun from snttaccept for registrar socket
...

Once the mwa.MaxLogFileSize=10000000 is met, a new log file should be created, but instead the system continues to write to the dispatcher.log

Changes

 None

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.