Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
A dynamic servant environment that is causing a job to hang in submit state after a new servant is brought.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of Compute Grid 8 on the z/OS * * platform. * **************************************************************** * PROBLEM DESCRIPTION: After a new servant region is brought * * up on an endpoint, the first job * * submitted to that endpoint hangs in * * submitted state. * **************************************************************** * RECOMMENDATION: * **************************************************************** After a new servant is brought up on an endpoint server, a new job immediately submitted to that endpoint hangs in submit state because the endpoint control region mbean is not up yet. This causes the endpoint to be marked as unavailable.
Problem conclusion
Instead of marking the endpoint as unavailable after one try, wait for the endpoint mbean to fully come up and retry. This fix is targeted for Compute Grid 8.0.0.4 and WAS fixpack 8.5.5.2
Temporary fix
Comments
APAR Information
APAR number
PM96645
Reported component name
WXD Z COMP GRID
Reported component ID
5655V6201
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-09
Closed date
2014-02-18
Last modified date
2014-03-12
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
WXD Z COMP GRID
Fixed component ID
5655V6201
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
27 April 2022