Maximo Open Forum

Related Content

  • 1.  Maximo Mobile Technician – todaywoassignedDS / MXAPIWODETAIL 504 Gateway Timeout (DB2 SQLCODE=-952)

    Posted 10 days ago
    Edited by RAJIBA GOUDA 8 days ago

    Hi Everyone,

    I'm troubleshooting an issue in Maximo Application Suite (Manage + Mobile Technician) and wanted to see if anyone has encountered something similar.

    Environment

    • MAS Manage / Mobile Technician
    • DB2 backend
    • Mobile Technician application
    • User login succeeds
    • Mobile application loads
    • Assigned Work Orders fail to load

    Mobile logs show:

    Datasource fetch failed
    RESTError2: Gateway Time-out
     
    Failed to load query
    RESTError2: Gateway Time-out
     
    [Error: Gateway Time-out]: performLoad failed
    Browser Network tab shows: 
    /oslc/os/mxapiwodetail

    returning: 

    504 Gateway Time-out
    Even a direct call to: 
    https://<server>/oslc/os/mxapiwodetail?lean=1 
    returns:
    504 Gateway Time-out
    The server didn't respond in time.
    Server Logs
    The Manage logs show:
    com.ibm.db2.jcc.am.SqlTimeoutException:
    Processing was cancelled due to an interrupt.
     
    SQLCODE=-952
    SQLSTATE=57014
    Stack trace points to:
    psdi.mbo.MboSet.getNextRecordData
    psdi.iface.mos.MboSetIterator.get
    OSOslcJsonSerializer.serializeResource
    OSGETRouteHandler.handleRequest
    which suggests the timeout occurs while Maximo is retrieving and serializing data from the object structure.
    SQL Identified

    I enabled SQL logging and found the query below associated with the failing datasource:

    select *
    from workorder
    where
    (
    (woclass='WORKORDER' or woclass='WOACTIVITY')
    and
    (
    (siteid='ABC' and worktype in ('PM','PROJ','BDM'))
    or
    (siteid<>'ABC' and worktype in ('PM','PROJ'))
    )
    and status not in ('MOBCOMP','COMP')
    and historyflag=0
    and istask=0
    and exists
    (
    select assignid
    from wfassignment
    where
    (
    assigncode='ABC1234'
    or assigncode in
    (
    select resppartygroup
    from persongroupteam
    where respparty='ABC1234'
    )
    )
    and ownertable='WORKORDER'
    and ownerid=workorder.workorderid
    and assignstatus in
    (
    select value
    from synonymdomain
    where domainid='WFASGNSTATUS'
    and maxvalue='ACTIVE'
    )
    )
    )
    order by wopriority
    for read only

    We're also seeing occasional timeouts against:

    MXAPITKCLASS
    savedQuery=MOBILECLASSSTRUCTURE
    which makes me wonder if this is:
    Missing DB2 indexes
    Poor query plan
    Large WFASSIGNMENT table
    Large PERSONGROUPTEAM table
    MXAPIWODETAIL customization
    Infrastructure timeout (Ingress/ALB)
    General database performance issue
    Questions :
    1. Has anyone seen SQLCODE=-952 / SQLSTATE=57014 during MXAPIWODETAIL processing?
    2. Was the root cause database indexing, object structure configuration, or infrastructure timeout?
    3. Did anyone identify specific indexes on:
      • WFASSIGNMENT
      • PERSONGROUPTEAM
      • WORKORDER that resolved similar Mobile timeout issues?
    4. Were there any custom relationships or child objects in MXAPIWODETAIL that caused excessive response time?
    5. How did you ultimately resolve the 504 Gateway Timeout?

    Any guidance, execution plan examples, or lessons learned would be greatly appreciated.

    Thanks!

    #Mobility

    ------------------------------
    RAJIBA GOUDA

    ------------------------------



  • 2.  RE: Maximo Mobile Technician – todaywoassignedDS / MXAPIWODETAIL 504 Gateway Timeout (DB2 SQLCODE=-952)

    Posted 10 days ago

    Hi Rajiba,

    It is highly likely that the root cause of your issue is linked to: "504 Gateway Time-out. Even a direct call to: https://<server>/oslc/os/mxapiwodetail?lean=1 "

    Replace the /oslc route with /api and use an API Key in the header. Example:

    GET https://mydomain/maximo/api/os/mxapiasset?lean=1&oslc.pageSize=10&oslc.select=assetnum,siteid,description
apikey: xxxxxxxxxx


    The issue is related to MAS Integration



    ------------------------------
    Fredrick Ndwaru
    Perpetual Ignition
    ------------------------------



  • 3.  RE: Maximo Mobile Technician – todaywoassignedDS / MXAPIWODETAIL 504 Gateway Timeout (DB2 SQLCODE=-952)

    Posted 7 days ago

    Thanks @FREDRICK NDWARU, attached more logs. Could you please check 



    ------------------------------
    RAJIBA GOUDA
    ------------------------------

    Original Message


  • 4.  RE: Maximo Mobile Technician – todaywoassignedDS / MXAPIWODETAIL 504 Gateway Timeout (DB2 SQLCODE=-952)

    Posted 7 days ago

    @RAJIBA GOUDA, can you test the Maximo Mobile APIs in https://www.ibm.com/docs/en/masv-and-l/maximo-manage/cd?topic=reference-maximo-mobile-rest-apis 

    1. First, test https://<server>/maximo/oslc/whoami from your UI after logging into Maximo. The expectation is an instant JSON response with your user details.
    2. Then test https://<server>/oslc/os/mxapiwodetail?lean=1&oslc.pageSize=10 from your UI. The expectation is a JSON response with the first ten WOs. Scroll to the bottom of the JSON response to view the page total, which should also include the total pages.  
    3. Finally, test  https://<server>/oslc/os/mxapiwodetail?lean=1; the expectation is a replication of the error or a response of all pages totaling the total pages
    4. To trigger and download a heap dump for a specific server instance or pod in Maximo Application Suite (MAS) 9.2 Manage, use the Maximo Management Interface (MMI) REST API endpoint: http://<host>:<port>/maximo/oslc/members/<memberid>/heapdump (or /maximo/api/members/<memberid>/heapdump). 
    5. Here is the MAS 9.2 link for additional Performance tips
      1. I've added the ignorecollectionref=1 query parameter to remove the collection ref to child collections from the response JSON to optimize further (2).   https://<server>/maximo/api/os/mxapiwodetail?lean=1&oslc.pageSize=10&ignorecollectionref=1


    ------------------------------
    Fredrick Ndwaru
    Perpetual Ignition
    ------------------------------

    Original Message


Newest Episode
Ep. 3 | Work Order Role-Based Application

Watch Steven Shull explore how Work Order Role-Based Applications in IBM Maximo can simplify work management, improve usability, and help teams focus on the right work order information.

Watch on YouTube Listen on Spotify
MORE by Naviam Episode 3 cover
Watch Episode 3
Also available: Ep. 2 | Adding a QR Code to a BIRT Report
Ep. 2 YouTube Ep. 2 Spotify Browse all episodes →