Fixes are available
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
Jobs dispatched to a newly defined endpoint cluster that has the same name as a previously deleted endpoint cluster will be stuck in the submitted state.
Local fix
Restart the scheduler
Problem summary
**************************************************************** * USERS AFFECTED: All users of Websphere Compute Grid 8.0 and * * beyond * **************************************************************** * PROBLEM DESCRIPTION: Jobs are stuck in submitted state when * * submitted to an endpoint cluster that * * was * * created using a previously deleted * * cluster name. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a cluster is created using the same cluster name of a previously deleted cluster, jobs submitted to an application on this new cluster will be stuck in or remain in submitted state.
Problem conclusion
Due to incomplete removal of the old cluster and creation of the new cluster from the Websphere Application Server administration framework, the new cluster appears unavailable to new job submissions. The creation process of the cluster was improved to successfully create the cluster from an administration point of view so that job submissions could occur successfully. The fix for this APAR is currently targeted for inclusion in fixpack 8.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27022998
Temporary fix
Comments
APAR Information
APAR number
PM96816
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-11
Closed date
2014-02-27
Last modified date
2014-03-31
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