IBM Support

IV85664: TICKETPRINT.RPTDESIGN SLOW OR FAILS ON MORE THAN ONE RECORD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Problem Details:
    Running ticketprint.rptdesign on more than one record causes
    high cpu
    load and out of memory
    When you run the report ticketprint.rptdesign on more records
    than one,
    it will cause high cpu use and out of memory error in Maximo.
    Steps to replicate:
    This was reproduced in a standard Maximo 7.6.0.4 environment.
    1. Log into Maximo with a user having access to the Service
    Request application (i.e. Wilson or Liberi.)
    2.  Go to Work Orders->Service Requests
    Or even Service Desk -> Service Requests application
    3.  Serach for records so that the list is limited to between
    2-50
    records.
    i.e. I selected 3 records.
    4. Go to Select Action -> Run report
    5.  Pick "Service Request Details".
    Maximo will now fail to generate the report and the job will
    stay
    running  indefinitely(?) in the REPORTJOB table with a high cpu
    load
    and the MxServer will slowly degenerate until it crashes.
    In other words, when submit the report the system  has message
    "processing, please wait.."  without any output  and is stuck
    on that.
    6. Now only select one record and it runs immediately
    As a workaround we have limited the report to only be allowed
    to run on
    one singe record.
    This can be reproduced in out of the box Maximo 7.6
    At 08:28:47 the report is executed
    At 08:39:46 the first report of a hung thread can be seen.
    The report is standard out of the box, and as I said in my
    first email
    you should quite easily be able to reproduce this problem if
    you follow
    the steps I provided.
    Product Version #:
    Tivoli's process automation engine 7.6.0.4 Build 20160316-1020
    DB Build V7604-37IBM TPAE Integration Framework 7.6.0.4 Build
    20160313-
    2330 DB Build V7604-22IBM Maximo Asset Management 7.6.0.4 Build
    20160310-1641 DB Build V7604-01
    IBM WebSphere Application Server 8.5.5.3
    Server DB  DB2/NT64 10.5 (SQL10050)
    Operating System:
    Windows 6.3
    

Local fix

  • Dev to provide fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * SR Details report users selecting more than one record       *
    * within Maximo                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Report ran slowly or experienced out of memory issues due to *
    * a bad loop condition                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Import the latest rptdesign file                             *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV85664

  • Reported component name

    BIRT INTEG-REPO

  • Reported component ID

    5724R46B1

  • Reported release

    760

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-13

  • Closed date

    2016-07-29

  • Last modified date

    2016-07-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCL37R","label":"BIRT"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6","Edition":""}]

Document Information

Modified date:
29 July 2016