IBM Support

JR44341: LOADING A HUMAN SERVICE IN PROCESS PORTAL TAKES LONG TIME IF MANY SNAPSHOTS ARE IN THE REPOSITORY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The following REST API call and corresponding method takes long
    time in BPM 8 if you have a rather big amount of data in
    lsw_snapshot table (typically in process center envs):
    
    REST:getTaskActions.......16:21:23:118-16:22:18:202 (  55084ms)
    period 55084ms 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canExecuteTasksActions
    
     In certain cases, the API call to retrieve the alllowed
    actions for tasks are expensive, in particular when the
    ACTION_INVITE is queried either explicitly (as part of a list
    of actions) or implicitly (when no list of actions is
    specified). The performance for retrieving this information
    from the underlying database may thereby degrade when the
    repository contains many snapshots (e.g. several thousands).
    This APAR improves the performance of this API call by caching
    the invariant information for each task definition; thus, only
    the first loading of a particular human service will require
    the expensive retrieval, whereas all subsequent requests for
    retrieving the actions for the same task definition will
    benefit from the cache.
    

Local fix

  • If at all possible clear down as much snapshots as possible
    using the delete process application feature in BPM.
    

Problem summary

  • Problem Description:
    Loading a human service in Process Portal takes long time if
    many snapshots are in the repository
    
    Problem Summary:
    The following REST API call and corresponding method takes long
    time in BPM 8 if you have a rather big amount of data in
    lsw_snapshot table (typically in process center envs):
    
    REST:getTaskActions.......16:21:23:118-16:22:18:202 (55084ms)
    period 55084ms 'EJB Calls'
    Method=AuthorizationAPIFacadeCore.canExecuteTasksActions
    
    In certain cases, the API call to retrieve the alllowed actions
    for tasks are expensive, in particular when the
    ACTION_INVITE is queried either explicitly (as part of a list of
    actions) or implicitly (when no list of actions is
    specified). The performance for retrieving this information from
    the underlying database may thereby degrade when the
    repository contains many snapshots (e.g. several thousands).
    
    Problem Conclusion:
    This APAR improves the performance of this API call by caching
    the invariant information for each task definition; thus, only
    the first loading of a particular human service will require the
    expensive retrieval, whereas all subsequent requests for
    retrieving the actions for the same task definition will benefit
    from the cache.
    

Problem conclusion

  • iFix available on top V800 GA
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44341

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-09

  • Closed date

    2012-12-12

  • Last modified date

    2012-12-12

  • 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



Document information

More support for: IBM Business Process Manager Standard

Software version: 8.0

Reference #: JR44341

Modified date: 12 December 2012