IBM Support

Mobile 8.10 - MobileDBGen cron task fails with Java OOM heap space error

Troubleshooting


Problem

The mobile version was upgraded from 8.8.0 to 8.10.0. Also, a few iFixes related to TPAE, Mobile, and GIS maps were installed. After this upgrade, heap dumps are generated on a regular basis. Once the heap dumps are generated, it makes the corresponding service down.
 

Diagnosing The Problem

Investigating further the heap dumps, it appears that when the Java Out-Of-Memory occurred, there were 5.1Gb objects on the heap with the largest consumers below, all allocated by thread "pool-15-thread-2" executing code for application MAXIMOUI:

Problem Suspect 1
117,815 instances of “psdi.plust.app.asset.PlusTAsset” occupy 1,581,296,168 (29.10%) bytes.  Most of these instances are referenced from one instance of “java.lang.Object[]” which occupies 2,971,344 (0.05%) bytes. The instance is referenced by “psdi.txn.MXTransactionImpl @ 0x73a8a3120”, loaded by “app:MAXIMOUI”.  These were allocated by thread "pool-15-thread-2" which has a local variable or reference to “psdi.plust.app.asset.PlusTAssetSet".
Problem Suspect 2
141,200 instances of “psdi.pluss.app.srvad.PlusSServiceAddress” occupy 1,301,301,184 (23.94%) bytes.  Most of these instances are referenced from one instance of “java.lang.Object[]” which occupies 2,971,344 (0.05%) bytes. The instance is referenced by “psdi.txn.MXTransactionImpl @ 0x73a8a3120”, loaded by “app:MAXIMOUI”. 
Thread “java.lang.Thread @ 0x6aadd3c00 pool-15-thread-2” has a local variable or reference to “psdi.plust.app.asset.PlusTAssetSet".
Problem Suspect 3
102,207 instances of “psdi.plust.app.location.PlusTLocation” occupy 646,968,216 (11.90%) bytes.  Most of these instances are referenced from one instance of “java.lang.Object[]” which occupies 2,971,344 (0.05%) bytes. The instance is referenced by “psdi.txn.MXTransactionImpl @ 0x73a8a3120”, loaded by “app:MAXIMOUI”. 

Resolving The Problem

Further investigation revealed a problem with FldAutolocatedGeometry calculation.  
To resolve the issue, the mxe.map.geometry.enableautolocate must be set to False, which is True by default.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAgaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EMobile"}],"ARM Case Number":"TS015725503","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Historical Number

TS015725503

Document Information

Modified date:
25 March 2024

UID

ibm17145136