Fixes are available
8.0.0.3: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 3
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
This APAR is to avoid repeated NullPointerExceptions in scheduler logs during resynchronization of job status on endpoint startup, because of inconsistencies in Compute Grid runtime tables
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Extended Deployment * * Compute Grid 8.0 and the batch function of * * WebSphere Application Server. * **************************************************************** * PROBLEM DESCRIPTION: Job ID table discrepancy results in * * logs filled with NullPointerException * * each time the scheduler resynchronize. * * [5/25/13 11:49:47:923 IST] 00000033 * * JobIDStoreImp 3 [SQL: SELECT * FROM * * LRSSCHEMA.GLOBALJOBIDASSIGNMENT WHERE * * JOBNUMBER = 988] * * [5/25/13 11:49:47:924 IST] 00000033 * * EndpointManag E Could not * * synchronize job status with endpoint: * * prcappa100prnoiNode01/prcappa100prnoiba * * tch01 error: null * * [5/25/13 11:49:47:925 IST] 00000033 * * SystemErr R * * java.lang.NullPointerException * **************************************************************** * RECOMMENDATION: * **************************************************************** The resynchronize process expects to find each job id it knows about and get its status from the Job Status table. If the job id is not found a NullPointerException is generated. This occurs at each resynchronize interval therefore filling up the logs with unnecessary error messages.
Problem conclusion
The resynchronize process captures the job id error correctly and logs it to the FFDC. The fix for this APAR is currently targeted for inclusion in Service Level (Fix Pack) 8.0.0.3 of WebSphere Compute Grid 8.0. 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
PM91323
Reported component name
WXD COMPUTE GRI
Reported component ID
5725C9301
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-18
Closed date
2013-08-13
Last modified date
2013-08-13
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 COMPUTE GRI
Fixed component ID
5725C9301
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 April 2022