Custom Logging Not Working After Log4j2 Upgrade
(Doc ID 2913446.1)
Last updated on DECEMBER 07, 2022
Applies to:
Oracle Communications Offline Mediation Controller - Version 12.0.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Application's logging not working for custom cartridges and java hooks after upgrade to log4j2. Prior to upgrade application's custom logging was through log4j1 where OCOMC was through log4j2, but after upgrading custom logging to log4j2, configurations loaded from custom log configurations are not taking effect.
From the debug console logs, it is clear that custom configurations are being loaded but when OCOMC (Oracle Communication Offline Mediation Controller) loads the OCOMCLogger.xml file it removes all the previously loaded configurations.
EXPECTED BEHAVIOR
-----------------------
After log4j upgrade should not impact custom configurations loaded.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade log4j2 from log4j1 version ,
2. Customize the custom cartridge by calling javahook with custom logging implementation
3. Start the cartridge
Changes
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 |