Fusion Client Log File Does Not Automatically Roll-Over/Split So the Log File is Growing Large and Has to be Manually Archived
(Doc ID 3042596.1)
Last updated on AUGUST 21, 2024
Applies to:
Oracle Retail Predictive Application Server - Version 16.0.3 and laterInformation in this document applies to any platform.
Symptoms
The Fusion Client log does not automatically roll-over/split even though the log4jconfig.xml contains the RollingFile appender.
Therefore the log file is growing large, it has reached 500MB in size and needs to be manually archived. Its indicated this should happen when the log reaches 50MB in size
This occurs in both Prod and Non-Prod environments since recent RPAS version update. It is requested to have this process occur automatically as before.
STEPS
The issue can be reproduced at will with the following steps:
1. Log into to Fusion Client.
2. Do activities to increase log file size until it reaches more than 50MB.
3. See log file is not rolled-over/split.
WORKAROUND
Manually stop the Fusion Client and manually archive the log file.
Changes
RPAS 16.0.3.274 update was applied.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |