IJ13140: SCHEDULER CRASH CAUSED BY GANTT MODEL NOT BEING CLEARED.

APAR status

• Closed as program error.

Error description

• Instances of MXGanttModel are not cleared from the cachedModels
  HashMap in SKDAppService. This leads to the HashMap continually
  growing in size until the heap is exhausted and leads to a
  crash.
  
  
  STEPS TO REPRODUCE:
  
  1) Log in as a user
  
  2) Open a schedule and navigate to the graphical view
  
  3) Check the size of the cachedModels HashMap instance
  
  4) Log out of the current session
  
  5) Log back in as the same user from step 1
  
  6) Open the same schedule as step 2 and navigate to the
  graphical view.
  
  7) Check the size of the cachedModels HashMap instance. It is
  now larger.
  
  RESULTS:
  
  This leads to the crash of the application server.
  
  REPORTED IN VERSION:
  
  Maximo 7.6.0.9 with Scheduler 7.6.7
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of the Graphical Scheduling application in Scheduler   *
  * 7.6.7.                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * SCHEDULER CRASH CAUSED BY GANTT MODEL NOT BEING CLEARED.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A code fix has been delivered to the stream.
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO SCHEDULE

• Fixed component ID

  5724R46SE

Applicable component levels

• R767 PSY

     UP