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
On a restart of a top level job, the analyzer SPI does not receive subjob collector data when the restarted top level job ran on a different endpoint server than its previous execution.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Compute Grid version 8.0 * **************************************************************** * PROBLEM DESCRIPTION: Analyzer SPI doesnot receive subjob * * collector data on restart. * **************************************************************** * RECOMMENDATION: * **************************************************************** On a restart, it is possible that a top level job would be executing on a different endpoint server than its previous execution. Since the subjob is not aware of the location of the top level job for this current execution, it does not send the collector data to this new location. It sends collector data to the original server.
Problem conclusion
On restart, the container will udpate the location of the top level job for all subjobs. 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=swg270 22998
Temporary fix
Comments
APAR Information
APAR number
PM97955
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-09-26
Closed date
2014-03-04
Last modified date
2014-03-04
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:
27 April 2022