Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
This problem was observed during high workload tests with WOLA and calls made from multiple IMS regions in parallel. The issues is triggered by the application calling over WOLA passing a wrong message data length each time it does a WOLA invoke BBOA1INV API call. This ultimately leads WebSphere to leak LSCBs. Once the LSCBPOOL in the pool created is exhausted, next StorageObtain returns -1 (7FFFFFF). WebSphere tries to use this pointer without checking the return code and it fails with abend S0C4: ------- ----------- PIDS/5655N0200 Program id: 5655N0200 RIDS/BBOOPCRT#L Load module name: BBOOPCRT RIDS/BBOCLSPC Csect name: BBOCLSPC AB/S00C4 System abend code: 00C4 PRCS/00000010 Abend reason code: 00000010 REGS/C36C0 Register/PSW difference for R0C:-36C0 RIDS/BBOCLSPC#R Recovery routine csect name: BBOCLSPC PSW@ points to instruction E50EE000 in this module: BBOOPCRT11.29 H28W700 Local Session PC .LSPCMAIN Instruction E50EE000 ==> => MVCSK R14,R0 Bad pointer in R14 - 7FFFFFFF Traceback for the failing TCB: Entry E Offset Statement Load Mod CALLWOLV +000008DC CALLWOLV IGZCFCC +000002C0 IGZCPAC CJTSTMAI +00001C5A CJTSTPSB CEEBPCAS +00000D0E CEEPIPI This APAR will also provide improved return/reason code indicating that the data pointer or length passed to WOLA BBOA1INV API is likely bad.
Local fix
Modify the application to send the proper message length.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: A ABEND in BBOCLSPC lead to the leak * * of LSCBs and dataspace cells in a * * WebSphere Application Server for z/OS * * Control region. * **************************************************************** * RECOMMENDATION: * **************************************************************** A WebSphere Optimized Local Adapter (WOLA) request (BBOA1INV), with an incorrect parameter value, may cause an ABEND in the WebSphere local communication PC routine--bboclspc. An ABEND within the Local communication PC routine may cause it to leak storage. There may be a leak of LSCBs (BBOCLSCB) and dataspace cells (dspname of "BBOCOMM") that the local communication code uses to process requests. An ABENDS0C4/ABEND0C4 can occur in the CopyStorage routine in BBOCLSPC. If the previous call to ObtainStorage failed to return storage (either a pointer to a dataspace cell or a pointer to above the bar storage), then the CopyStorage routine will ABEND. There is no check against the returned pointer.
Problem conclusion
Code has been modified to add more recovery code to track and release the allocated dataspace cells and allow for the freeing of LSCBs. APAR PM59352 is currently targeted for inclusion in WebSphere Application Server V7.0 Fix Pack 7.0.0.25 and WebSphere Application Server V8.0 Fix Pack 8.0.0.4. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM59352
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-29
Closed date
2012-03-13
Last modified date
2012-11-02
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK81738
UP12/10/04 P F210
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.
Document Information
Modified date:
28 October 2021