IBM Support

JR45671: HIGH CPU UTLIIZATION WHILE UPDATING TIMING INTERVALS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the Performance Data Warehouse, periodic timing interval
    updates may cause high CPU utilization.  This has been observed
    under the following conditions:
    
    - High number of timing intervals
    - Long running BPDs
    - BPDs contain loops that cause timing intervals to be reached
    multiple times
    
    Environments that contain the fix for APAR JR43262 are
    more susceptible to this issue, as the fix shifted logic that
    excludes timing intervals that do not need to be updated from a
    database query (SELECT statement) to the performance server.
    (BPM Versions 7.5.1.1 and 8.0.1.0 contain the JR43262 fix, and
    there are currently JR43262 interim fixes for Versions
    7.5.0.1, 7.5.1.0, and 8.0.0.0.)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Advanced, BPM Standard, and    *
    *                  BPM Express.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: In the Performance Data Warehouse,      *
    *                      periodic timing interval updates may    *
    *                      cause high CPU utilization.  This has   *
    *                      been observed under the following       *
    *                      conditions:                             *
    *                      - High number of timing intervals       *
    *                      - Long running BPDs                     *
    *                      - BPDs contain loops that cause         *
    *                      timing intervals to be reached          *
    *                      multiple times                          *
    *                      Environments that contain the fix for   *
    *                      APAR JR43262 are more susceptible to    *
    *                      this issue, as the fix shifted logic    *
    *                      that excludes timing intervals that     *
    *                      do not need to be updated from a        *
    *                      database query (SELECT statement) to    *
    *                      the performance server. (BPM Versions   *
    *                      7.5.1.1 and 8.0.1.0 contain the         *
    *                      JR43262 fix, and there are currently    *
    *                      JR43262 interim fixes for Versions      *
    *                      7.5.0.1, 7.5.1.0, and 8.0.0.0.)         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The fix for APAR JR43262 improved database performance with a
    high number of timing intervals, but there was an additional
    performance issue in the performance server code that was
    exacerbated when shifting more of the timing interval exclude
    logic from database to server.
    

Problem conclusion

  • The maximum number of timing intervals that can be included
    in a single database SQL query WHERE clause during post load
    calculation and which can be safely handled by a database was
    made configurable.  In case the number of entries exceeds the
    configurable limit, then filtering of timing intervals is
    executed in performance server code instead of the database
    query.
    
    An interim fix for JR45671 is available for Business Process
    Manager Versions 7.5.1.0, 7.5.1.1, and 8.0.0.0.  Please refer
    to the separate file that is automatically downloaded with
    the interim fix for prerequisite information and
    installation/uninstallation instructions.
    
    The JR45671 fix is also included in the Business Process
    Manager 8.0.1.1 fix pack and the 8.5.0.0 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR45671

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-06

  • Closed date

    2013-04-26

  • Last modified date

    2014-02-21

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R800 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0"}]

Document Information

Modified date:
07 October 2021