AAI jaws.log stops writing after server is offline during midnight rollover

Products

• Automation Analytics & Intelligence

Issue/Introduction

After an AAI server reboot or a period of downtime that spans across midnight, users may observe the following:

• The active jaws.log file stops being updated with new data.
• The previous day's rotated log file (e.g., jaws.log.YYYY-MM-DD) contains exactly one line of log data from the current day.
• A directory listing shows the jaws.log file size is small (e.g., ~100 bytes) and not growing despite the application being active.
• Standard log entry example found in the wrong file: 2026-07-07 07:34:06,061 INFO [DatabaseType] Could not find URL key for Database Sybase (jConnect driver)

Cause

This behavior is due to a defect in the log rotation logic (tracked as DE208837). When the AAI service is offline during the midnight transition, the logging framework fails to correctly initialize the new day's log file upon startup. It incorrectly appends the initial startup entries to the last known rotated file and then loses the active file handle, preventing further logging.

Resolution

This issue is currently under investigation by Engineering. A permanent fix will be included in a future release.

Workaround

To resume normal logging, perform a secondary restart of the AAI application service:

1. Stop the AAI application service.
2. Start the AAI application service.
3. Monitor the jaws.log file to confirm it is now actively receiving updates with the current timestamp.

Note: This issue is typically only encountered if the server remains down during the midnight rollover. Normal reboots that occur within the same calendar day do not trigger this defect.

---