Fixes are available
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
During shutdown of CICS regions with embedded liberty servers running at a mix of 16.0.0.3 and 17.0.0.3 service levels, a crash in the liberty supplied TRUE BBOATRUE was reported. The crash is in function angelClientInvokeStub(). The issue is due to 17.0.0.3 code referencing past the end of a control block that was allocated by 16.0.0.3 code. The control block is 8 bytes bigger in 17.0.0.3 than it was in 16.0.0.3 -- From the CICS side the reported externals will show: Error Code: 0C4/AKEA Error Type: PROGRAM CHECK Execution key at Program Check/Abend: 8 Instruction Length: 6 Interrupt Code: 0038 Branch Event Address: 172B2CE8 Module BBOACALL + X'1A0' CICS Error Instruction Address: 172B2D5E Module BBOACALL + X'216'
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty for z/OS * **************************************************************** * PROBLEM DESCRIPTION: WOLA client gets an 0c4 abend in * * angelClientInvokeStub() when running at * * a mix of 16.0.0.3 and 16.0.0.4 or * * higher. * **************************************************************** * RECOMMENDATION: * **************************************************************** WOLA client gets an 0c4 abend when 16004 code tries to use a field that is past the end of the a control block that was allocated by 16003 code. The size of the WolaClientBindInformation_t control block increased in 16004 when a field called angelAnchor_p was added. The 0c4 abend occurrs when a 16003 WOLA client registers and creates the control block at the 16003 size, a server is started at 16004 or later and then the WOLA client unregisters. Durring the unregister the 16004 or later code gets control and abends when it tries to use angelAnchor_p. angelAnchor_p is unpredictable because it depends on what got allocated after the 16003 sized control block.
Problem conclusion
Updated the code to not reference angelAnchor_p when the WolaClientBindInformation_t control block is the smaller 16003 size. The fix for this APAR is currently targeted for inclusion in fix pack 18.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI92868
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-24
Closed date
2018-02-16
Last modified date
2018-02-16
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
LIBERTY PROF -
Fixed component ID
5655W6514
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022