Fixes are available
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The ORBR Large Cellpool (index 3) was the target of the expansion. The ORBR cellpool info area indicates that the computed number of cells per extent was "1". This is too small of a number and lead to the ABEND. The servant was configured with the server_region_workload_profile=ISOLATE; this means "1" WLM Application Thread in the Servant. . However, there is work executing under this server outside of the typical WLM Threads (more work than typical) on the Internal Thread Pool. This pools was increased form its default of 3 threads to 10 threads. . What happened was that the ORBR Large cellpool needed to expand. It obtained storage and added it to the pool but before it could get a cell out of the pool (remember the newly added extent only has 1 cell) another thread in the servant got the Cell. The failure to obtain a cell after expanding the pool is what produced the ABENDEC3. . The ORBR cellpool information should be set up to apply a reasonable minimum amount of cells per extent. The current calculation multiples is based on the number of WLM Application Threads configured. We should also expand this calculation to include the Internal Thread Pool.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application server for z/OS * * Servant received ABENDEC3,RSN=0406002E * **************************************************************** * RECOMMENDATION: * **************************************************************** A native managed request based cellpool extent was created with 1 cell. A cell request was made to the pool and caused an expansion. After expanding the cellpool with another extent another cell request was made which also failed to retrieve a cell. The reason is that other work in the Servant had retrieved the 1 newly added cell before the previous caller had the chance. Failure to retrieve a cell after expanding the cellpool with another extent resulted in the ABEND EC3. The number of cells configured for the extent is too small.
Problem conclusion
Code has been modified to ensure that a more reasonable number of cells is used for the native request based cellpools. APAR PI38104 is currently targeted for inclusion in Fix Packs 8.0.0.11 and 8.5.5.7 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI38104
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-03-30
Closed date
2015-04-17
Last modified date
2015-04-17
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
R800 PSY
UP
Document Information
Modified date:
28 April 2022