PI35769: HEAP GROWTH IN JOB SCHEDULER CAUSED BY NON-WSGRID JOB NOTIFICATI ONS.

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.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

• When WSGrid is installed, submitting non-wsgrid jobs causes
  heap growth in the Job Scheduler.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server version 8.5 WSGrid Batch             *
  *                  functionality.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When WSGrid is installed, submitting    *
  *                      jobs through means other than WSGrid    *
  *                      (lrcmd or Job Management Console)       *
  *                      causes heap growth in the Job           *
  *                      Scheduler.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the JobSchedulerMDB, a JMXListener is registered to listen
  for job life cycle events.  If a "started" notification is
  received before the receipt of a jobid for the job, the
  notification is added to a "early notifications" table.
  Once the jobid is received and the JobWatcher is created, the
  early notifications are processed and the entry is removed
  from the "early notificatons" table.
  However, the JMXListener receives notifications for all jobs,
  including those that were not submitted through wsgrid.
  Since the JobSchedulerMDB is not monitoring these jobs, a
  jobid is not registered for them. So, when the notification
  comes into the listener, it is added to the "early
  notifications" table since it is believed to be an early
  notification.  Since the submit was not done through the
  the JobSchedulerMDB, a JobWatcher is never created and the
  entry is never removed.
  

Problem conclusion

• The code was changed to check to see if the notification
  received was for a wsgrid job. If it is for a non-wsgrid job,
  the notification is not added to the "early notifications"
  table.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• 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