Fixes are available
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.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
Output queue cleanup processing running on multiple schedulers can result in attempts to purge the same job more than once. The purge succeeds, but server logs can be filled with error output depending on the timing.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the WebSphere Batch Function of * * IBM WebSphere Application Server V8.5. * **************************************************************** * PROBLEM DESCRIPTION: Extraneous output during duplicate * * purge * * operation * **************************************************************** * RECOMMENDATION: * **************************************************************** When the purge command is issued to purge a job that runs on a different endpoint than the one that the purge command is submitted on there are sometimes NullPointerException being thrown.
Problem conclusion
This error was not causing any issues with the batch application, but was cluttering up the logs with errors and exceptions. The issue was that when a purge command was submitted on a different endpoint than the endpoint the job ran on that is to be purged the job would try to purge itself twice. This issue was fixed by checking for null on the endpoint side where the purge command was issued. APAR PI27492 is currently targeted for inclusion in fix pack 8.5.5.4 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27022998
Temporary fix
An interim fix is available upon request.
Comments
APAR Information
APAR number
PI27492
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-10-13
Closed date
2014-11-12
Last modified date
2014-11-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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022