IJ06204: Maximo server crashes as a result of many BMXAA6713E errors

APAR status

• Closed as program error.

Error description

• ERROR
  BMXAA6713E - THE MBO FETCH OPERATION FAILED IN THE MBOSET WITH
  THE SQL ERROR CODE -4470
  PROBLEM DESCRIPTION
  The server crashes as a result of many BMXAA6713E errors.
  Millions of entries of this error in the log eventually causes
  the JVM to crash.
  From a java core analysis the application tries to reload
  MAXLABEL cache and during that activity block all other
  threads. The reason for it looping is a database leak.
  Possibly related to class:
  psdi.webclient.system.controller.LabelCacheMgr.class
  It has not been possible to associate the end user actions to
  the JVM eventually going down.
  Rebooting the database is a work-around.
  Environment settings / details:
  The current settings on affected environment:
  mxe.db.closelongrunconn: false
  mxe.db.longruntimelimit: 180
  mxe.db.detectlongrunconninterval: 0
  There are 33 UI JVMs -- on 3 UI dedicated nodes (11 per node).
  No MIF / Reporting / Crons is running on UI nodes.
  There are no other application/services that could consume
  resources.
  The JVM has 4 GB for heap memory
  Gencon policy (1 GB of nursery and 3 GB of tenured area)
  Identified in an environment with
  ICD 7.6.0.1049
  DBDB2/LINUXX8664 10.5 (SQL10058)
  Tivoli's process automation engine 7.6.0.3-IFIX20170120-1436
  Build 20160113-2204 DB Build V7603-151 HFDB Build HF7603-08
  

Local fix

• Reboot the database decreased the frequency
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * N/A                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * BMXAA6713E - THE MBO FETCH OPERATION FAILED IN THE MBOSET    *
  * WITHTHE SQL ERROR CODE -4470                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in LabelCacheMgr.java
  

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

  ASSETS

• Fixed component ID

  5724R46AS

Applicable component levels

• R760 PSY

     UP