Fixes are available
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
Heap growth is observed in the Job Scheduler servant region when running Parallel Job Manager (PJM) jobs using WSGrid.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 Parallel Job Manager Batch * * function using WSGrid to submit jobs. * **************************************************************** * PROBLEM DESCRIPTION: When using WSGrid to submit Parallel * * Job Manager jobs, heap growth will be * * observed in the Job Scheduler. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem occurs with ParallelJobManager (PJM) jobs submitted through WSGrid. The JMXListener receives notifications for all jobs, including PJM subjobs. é á Since the JobSchedulerMDB is no monitoring these jobs, a JobWatcher is not created for them. Therefore, when the notification comes into the listener, the job is added to a HashMap under the assumption that an early notification for the job was received. Since the job submission for these jobs was not done through the JobSchedulerMDB, the entry is never removed from the HashMap.
Problem conclusion
The code has been changed to detect that a notification is for a PJM subjob and not add an entry to the early notification HashMap. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27036319
Temporary fix
Comments
APAR Information
APAR number
PI33945
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-02-02
Closed date
2015-02-12
Last modified date
2015-02-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:
27 April 2022