APAR status
Closed as program error.
Error description
Customer upgraded from SI 5.2.5 to 5.2.6.4. They observed the following error in noapp.log: [2019-11-05 11:51:39.966] ALL 000000000000 GLOBAL_SCOPE ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... We checked the dynamicclasspath.cfg and also the output of command "ls -altR" from the SI install dir and we did not find any reference to log4j-core. So we cannot put it to the classpath as requested in the above error message.
Local fix
Problem summary
Users Affected: All Problem Description: Found the following error in noapp.log: [2019-11-05 11:51:39.966] ALL 000000000000 GLOBAL_SCOPE ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... Platforms Affected: All
Problem conclusion
Resolution Summary: The issue is resolved by adding log4j-core to the classpath. A code fix is provided. Delivered in: 5020605_4 6000007
Temporary fix
Comments
APAR Information
APAR number
IT33075
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
526
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-06-04
Closed date
2021-07-29
Last modified date
2021-07-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6"}]
Document Information
Modified date:
30 July 2021