IBM Support

JR63461: SAVING OR PLAYING BACK IS SLOW WHEN YOU USE THE WEB IBM PROCESS DESIGNER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Depending on the content in your application, you might find
    that saving changes or debugging an application by performing a
    playback is very slow in your environment. When there are many
    developers, slow saves and playbacks can block other users from
    doing their work and lead to warning messages, such as the
    "Saving Editors" messages.
    
    If you turn on
    'WLE.wle_webpd.scheduler.sql=all:WLE.wle_bpmrest.sql=all'
    traces, you might see duplicates SQL calls with the same
    parameters during one save against lsw_branch and
    lsw_project_dependency table, such as in this example:
    
    select
    BRANCH_ID,CREATED_ON,LAST_MODIFIED,ARCHIVED_ON,NAME,ACRONYM,DESC
    RIPTION,TIP_SEQ_NUM,CREATED_BY_USER_ID,LAST_MODIFIED_BY_USER_ID,
    TIP_SNAPSHOT_ID,PROJECT_ID,BASE_SNAPSHOT_ID,IS_ARCHIVED,IS_DEFAU
    LT from LSW_BRANCH where BRANCH_ID = ?
    args:aaaaaaaaa-bbbb-cccc-dddd-xxxxxxxxxxxx
    select
    PROJECT_DEPENDENCY_ID,VERSION_ID,LATEST_SNAPSHOT_SEQ_NUM,RANK,NA
    ME,DESCRIPTION,LAST_MODIFIED,TARGET_SNAPSHOT_ID,LAST_MODIFIED_BY
    _USER_ID,IS_SYSTEM,IS_ACTIVE,IS_MANAGED from
    LSW_PROJECT_DEPENDENCY where ROJECT_DEPENDENCY_ID = ? and
    version_id = ? args: xxxxxx , yyyyy
    select
    BRANCH_ID,CREATED_ON,LAST_MODIFIED,ARCHIVED_ON,NAME,ACRONYM,DESC
    RIPTION,TIP_SEQ_NUM,CREATED_BY_USER_ID,LAST_MODIFIED_BY_USER_ID,
    TIP_SNAPSHOT_ID,PROJECT_ID,BASE_SNAPSHOT_ID,IS_ARCHIVED,IS_DEFAU
    LT from LSW_BRANCH where BRANCH_ID = ?
    args:aaaaaaaaa-bbbb-cccc-dddd-xxxxxxxxxxxx
    select
    PROJECT_DEPENDENCY_ID,VERSION_ID,LATEST_SNAPSHOT_SEQ_NUM,RANK,NA
    ME,DESCRIPTION,LAST_MODIFIED,TARGET_SNAPSHOT_ID,LAST_MODIFIED_BY
    _USER_ID,IS_SYSTEM,IS_ACTIVE,IS_MANAGED from
    LSW_PROJECT_DEPENDENCY where PROJECT_DEPENDENCY_ID = ? and
    version_id = ? args: zzzzzz ,vvvvv
    

Local fix

  • To improve performance, follow these suggestions:
    
       -Run the BPMSnapshotCleanup command frequently or enable
    <unnamed-snapshots-cleanup-config> to reduce number of unnamed
    snapshots in your environment. For more information, see
    "BPMSnapshotCleanup command"
    (https://www.ibm.com/docs/en/baw/20.x?topic=scripting-bpmsnapsho
    tcleanup) or "Deleting unnamed snapshots in bulk from a Workflow
    Center server"
    (https://www.ibm.com/docs/en/baw/20.x?topic=method-deleting-unna
    med-snapshots-in-bulk-automated).
        -Avoid many developers working on same branch at same time
    by, for example, moving some assets from the main process app to
    a toolkit.
        -Click "Finish editing" first, wait a while, and then click
    "Run" to reduce the number of unnamed snapshots created.
    

Problem summary

  • This issue occurs when a playback tries to save the pending
    changes to create an unnamed snapshot. As a result, the playback
     makes multiple duplicate calls to lsw_branch and
    lsw_project_dependency tables, which causes slow performance.
    
    PRODUCT AFFECTED
    IBM Business Automation Workflow
    

Problem conclusion

  • A fix is available or will be available that reduces the
    duplicate calls by using internal caching during a playback
    save.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR63461

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    K00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-18

  • Closed date

    2021-04-07

  • Last modified date

    2021-04-07

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"20.0.0.1"}]

Document Information

Modified date:
08 October 2021