Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

Maximo Mobile DB generation Java heap size error

  • 1.  Maximo Mobile DB generation Java heap size error

    Posted 3 days ago
      |   view attached

    Hi Everyone,

    We have upgraded Maximo 7.6 environment to MAS 9.0.9 and since the upgrade Maximo Mobile DB generation is not working. Crontaks is running 1 hour and failing with Java heap space error. See attached pic and here are some details from the log:

    14 Nov 2025 07:22:56:986 [DEBUG] [localhost] [] MMDBLog - MobileDBGenCallable.getData - finally - MAXTABLEDOMAINVAL - MXMMOBIL
    [err] : 
    [err] Java heap space
    [err]     at 
    [err] java.base
    [err] /
    14 Nov 2025 07:22:56:988 [DEBUG] [localhost] [] MMDBLog - MobileDBGenCallable.call - Start - NUMERICDOMAIN - MXMMOBIL
    [ERROR   ] SRVE8109W: Uncaught exception thrown by filter XAccessTokenFilter: java.lang.OutOfMemoryError: Java heap space
        at java.base/java.lang.Class.getMethodImpl(Native Method)
        at java.base/java.lang.Class.getMethodHelper(Class.java:1535)
        at java.base/java.lang.Class.getMethod(Class.java:1441)
        at psdi.webclient.system.filter.XAccessTokenFilter.getRawIdToken(XAccessTokenFilter.java:154)
        at psdi.webclient.system.filter.XAccessTokenFilter.doFilter(XAccessTokenFilter.java:91)
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:203)
        at [internal classes]

    14 Nov 2025 07:23:01:256 [DEBUG] [localhost] [] MMDBLog - MobileDBGenCallable.getData - do while - processing page 1 - NUMERICDOMAIN - MXMMOBIL
    14 Nov 2025 07:23:01:256 [DEBUG] [localhost] [] MMDBLog - MobileDBGenCallable.getData - do while - processing page 1 - NUMERICDOMAIN - MXMMOBIL
    [err] LoggingService.java
    [err] :
    [err] 3
    [err] 8
    [err] 4
    [err] )
    [err] psdi.util.MXSystemException: BMXAA4160E - A major exception has occurred. Check the system log to see if there are any companion errors logged. Report this error to your system administrator.
        Java heap space
    [err]     at psdi.server.AppService.getMboSet(AppService.java:541)
    [err]     at psdi.server.MXServer.getMboSet(MXServer.java:2760)
    [err]     at psdi.util.logging.LoggingService$LogUploadReqMonitor.run(LoggingService.java:384)
    [err] Caused by: 
    [err] java.lang.OutOfMemoryError
    [err] : 
    [err] Java heap space
    [err]     at 
    [err] java.base
    [err] /
    [err] java.lang.Class
    [err] .
    [err] getConstructorImpl
    [err] (
    [err] Native Method
    [err] )
    [err]     at 
    [err] java.base
    [err] /
    [err] java.lang.Class
    [err] .
    [err] getConstructor
    [err] (
    [err] Class.java
    [err] :
    [err] 6
    [err] 8
    [err] 8
    [err] )
    [err]     at 
    [err] psdi.server.AppService
    [err] .
    [err] getMboSet
    [err] (
    [err] AppService.java
    [err] :
    [err] 4
    [err] 9
    [err] 4
    [err] )
    [err]     ... 
    [err] 2
    [err]  more
    14 Nov 2025 07:23:01:265 [ERROR] [localhost] [] Java heap space
    java.lang.OutOfMemoryError: Java heap space
        at jdk.internal.reflect.ByteVectorImpl.<init>(ByteVectorImpl.java:37) ~[?:?]
        at jdk.internal.reflect.ByteVectorImpl.<init>(ByteVectorImpl.java:33) ~[?:?]
        at jdk.internal.reflect.ByteVectorFactory.create(ByteVectorFactory.java:30) ~[?:?]
        at jdk.internal.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:134) ~[?:?]
        at jdk.internal.reflect.MethodAccessorGenerator.generateConstructor(MethodAccessorGenerator.java:92) ~[?:?]
        at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:55) ~[?:?]
        at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
        at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?]
        at psdi.mbo.Mbo.generateMboValueInstance(Mbo.java:940) ~[businessobjects.jar:?]
        at psdi.mbo.Mbo.getMboValue(Mbo.java:1214) ~[businessobjects.jar:?]
        at psdi.mbo.Mbo.getString(Mbo.java:2109) ~[businessobjects.jar:?]
        at psdi.server.CronMonitorCronTask.cronAction(CronMonitorCronTask.java:58) [businessobjects.jar:?]
        at psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:2594) [businessobjects.jar:?]
        at psdi.server.CronTaskManager.access$1100(CronTaskManager.java:107) [businessobjects.jar:?]
        at psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:3513) [businessobjects.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:839) [?:?]

    We have tried to recreate the cron task, reload, change the parameters but nothing helped. We tried to change maximo.mobile.db.gen.dir and mxe.int.globaldir system properties but nothing helped.

    If you have ever faced this kind of issue don't hesitate to contact me! Thank you in advance!

    Cheers,

    Levi



    ------------------------------
    Levente Molnár
    ------------------------------