A fix is available
APAR status
-
Closed as program error.
Error description
-
After migrating to Liberty 19.0.0.3 CICS experiences an increase in CPU consumption. Health Center data shows that method org.eclipse.osgi.internal.log.LoggerImpl.getLocation() is consuming a large (50%+) amount of the CPU cycles of those sampled. To circumvent this problem update server.xml to include: <logging traceSpecification="logservice=info"/> or <logging traceSpecification="logservice=warning"/>
Local fix
-
add the following line to the Liberty server.xml: <logging traceSpecification="logservice=info"/> If such a tag already exists, then append :logservice=info to the value.
Problem summary
-
**************************************************************** * USERS AFFECTED: All CICS users with any of the following * * PTFs applied: * * * * CICS TS 5.1: UI63151 * * CICS TS 5.2: UI63153 * * CICS TS 5.3: UI63157 UI67364 * * CICS TS 5.4: UI63155 UI67366 * * CICS TS 5.5: UI63159 UI64379 UI66360 * **************************************************************** * PROBLEM DESCRIPTION: Liberty startup performance * * degradation. * **************************************************************** After applying the PTFs for CICS Liberty 19.0.0.3, 19.0.0.6, 19.0.0.9 or 19.0.0.12 Liberty JVMSERVERs and applications take longer to start. This is as a result of changes to the Equinox OSGi logging service which were included in Liberty 19.0.0.3. Health Center Method Profiling analysis of an affected JVMSERVER will show very high execution of org.eclipse.osgi.internal.log.LoggerImpl.getLocation().
Problem conclusion
-
UI63151 UI63153 UI63157 UI67364 UI63155 UI67366 UI63159 UI64379 UI66360 The version of CICS Liberty has been updated to 20.0.0.3. This includes the fix for Open Liberty issue 10412 which prevents the performance impact described above.
Temporary fix
Comments
APAR Information
-
APAR number
PH20006
-
Reported component name
CICS TS Z/OS V5
-
Reported component ID
5655Y0400
-
Reported release
000
-
Status
CLOSED PER
-
PE
YesPE
-
HIPER
YesHIPER
-
Special Attention
NoSpecatt / Xsystem
-
Submitted date
2019-12-06
-
Closed date
2020-05-20
-
Last modified date
2020-06-01
-
APAR is sysrouted FROM one or more of the following:
-
APAR is sysrouted TO one or more of the following:
Modules/Macros
-
DFHAPJVM DFHAPLJP DFHAXIS2 DFHCAL64 DFHCDJNI DFHCDK64 DFHKETIX DFHSJBD DFHSJDM DFHSJDS DFHSJDUF DFHSJIN DFHSJIS DFHSJIX DFHSJJS DFHSJL DFHSJLOG DFHSJNA DFHSJNDI DFHSJNR DFHSJNT DFHSJPP DFHSJPTI DFHSJRE DFHSJRL DFHSJRM DFHSJRT DFHSJSA DFHSJSC DFHSJSM DFHSJSR DFHSJST DFHSJTE DFHSJTH DFHSJTRI DFHSJWL DFHSJXM DFHWLPAX DFJ@H350 DFJ@H356 DFJ@H360 DFJ@H387 DFJ@H427 DFJ@H448 DFJ@H467 DFJ@H468 DFJ@H561 DFJDTCOE DFJOUTRE DFJWLPBP DFJWLPPL
Fix information
-
Fixed component name
CICS TS Z/OS V5
-
Fixed component ID
5655Y0400
Applicable component levels
-
R00L PSY UI69614
UP20/05/21 P F005
-
R10L PSY UI69610
UP20/05/23 P F005
-
R20L PSY UI69617
UP20/05/23 P F005
-
R80L PSY UI69609
UP20/05/27 P F005
-
R90L PSY UI69612
UP20/05/28 P F005
Fix is available
-
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
27 July 2020