Need Information About Clearing Tmp Logs Generated By Osm In Weblogic
(Doc ID 3015748.1)
Last updated on APRIL 18, 2024
Applies to:
Oracle Communications Order and Service Management - Version 7.4.0.0.0 and laterInformation in this document applies to any platform.
Goal
On : 7.4.0.0.0 version, BEA Server
Need information about clearing tmp logs generated by OSM in Weblogic
The customer using OSM 7.4.0 in their application and it is working fine without issues.
But it is generating temporary logs when we restart the application which was using log4j-1.2.17.jar.
Below are the path details.
Due to this, these were detected by quality team as vulnerabilities which are considered security risks by a central team.
Already application log4j was upgraded to log4j-2.17.2 in our system.
Since the below are OSM dependencies, we need your help to fix this issue.
This is showing on all Live and Non-live environments.
PATH VERSION JMS__CLASS__STATUS BASE__DIR
/wls_domains/rgv21jup/tmp_managed2_rgv21jup/vfs_cache_rgv21jup/tmp_23742_osmmodel/JobControl/1.0.0.0.0/resources/log4j-1.2.17.jar 1.2.17 JMSAppender_CLASS_FOUND /wls_domains/rgv21jup/tmp_managed2_rgv21jup
/wls_domains/rgv21jup/tmp_managed2_rgv21jup/vfs_cache_rgv21jup/tmp_46618_osmmodel/JobControl/1.0.0.0.0/resources/log4j-1.2.17.jar 1.2.17 JMSAppender_CLASS_FOUND /wls_domains/rgv21jup/tmp_managed2_rgv21jup
/wls_domains/rgv21jup/tmp_managed2_rgv21jup/vfs_cache_rgv21jup/tmp_5369_osmmodel/JobControl/default/resources/log4j-1.2.17.jar 1.2.17 JMSAppender_CLASS_FOUND /wls_domains/rgv21jup/tmp_managed2_rgv21jup
/wls_domains/rgv21jup/tmp_managed2_rgv21jup/vfs_cache_rgv21jup/tmp_7183_osmmodel/JobControl/1.0.0.0.0/resources/log4j-1.2.17.jar 1.2.17 JMSAppender_CLASS_FOUND /wls_domains/rgv21jup/tmp_managed2_rgv21jup
Solution
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
| Goal |
| Solution |