IBM Support

JR51895: YOU EXPERIENCE A PERFORMANCE ISSUE WHEN YOU RUN A HUMAN SERVICE THAT HAS A HIGH NUMBER OF COMPLEX BUSINESS OBJECTS VARIABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you run a human service that has a high number of complex
    business objects variables, the response time increases when you
    trigger a boundary event. If the business object definitions are
    not in the same toolkit or process application as the human
    service the response time is even longer.
    The performance impact to users may be system wide or with a
    cerain set of users or processes running on the system.
    There are several indications in logs and traces which
    demonstrate this problem. One or more of these may be present
    in data collected.
    1) This set of logs repeated many times (1000s) with a
    WLE.*=all trace
    [24/11/14 20:02:44:958] 00000198 wle_versionin  X
    com.lombardisoftware.server.ejb.persistence.versioning.SnapshotC
    ontextManagerincrementUsageCount
    Snapshot.3c71eb1e-a063-43bf-9a2e-2abd810fa3fb
     increment usage count to 1
    [24/11/14 20:02:44:958] 00000198 wle_versionin  X
    com.lombardisoftware.server.ejb.persistence.versioning.SnapshotC
    ontextManageracquireSnapshotContext acquire context
    Snapshot.3c71eb1e-a063-43bf-9a2e-2abd810fa3fb
    [24/11/14 20:02:44:958] 00000198 wle_versionin  X
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImplreadAccess calling read callback
    withSnapshot.3c71eb1e-a063-43bf-9a2e-2abd810fa3fb
    [24/11/14 20:02:44:958] 00000198 wle_versionin  X
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImplreadAccess
    Snapshot.3c71eb1e-a063-43bf-9a2e-2abd810fa3fb
    released after read
    [24/11/14 20:02:44:958] 00000198 wle_versionin  X
    com.lombardisoftware.server.ejb.persistence.versioning.SnapshotC
    ontextManagerdecrementUsageCount
    Snapshot.3c71eb1e-a063-43bf-9a2e-2abd810fa3fb
    decrement usage count to 0
    2)
     If tracing there may also be multiple (repeated) messages such
    as
    [11/8/15 22:15:20:653 EST] 00000114 wle           3
    setActivationVersioningContextOnObject is not called for unknown
     object of class class java.lang.String
    [11/8/15 22:15:20:653 EST] 00000114 wle           3
    setActivationVersioningContextOnObject is not called for unknown
    object of class class java.lang.String
    3) large time difference with DeltaUtils compare function
    [2/2/17 17:01:04:558 CST] 00000418 wle           >
    com.lombardisoftware.core.util.DeltaUtils compare ENTRY
    [2/2/17 17:01:58:109 CST] 00000418 wle           <
    com.lombardisoftware.core.util.DeltaUtils compare RETURN
    List<DeltaItem>, length: 0
    

Local fix

Problem summary

  • When a human service navigates from one coach to the next, it
    accesses variables. When these variables are typed by complex
    business objects, the human service must look up the
    corresponding business object definition. The lookup action
    takes time, especially when the business object definition is in
    a different context than the human service.
    

Problem conclusion

  • A fix is available that allows you to enable a cache in
    the 100Custom.xml file to optimize the lookup action:
     <server merge="mergeChildren">
        <twobject-class-cache-size>{int value}
        </twobject-class-cache-size>
     </server>
    Guidance for determining a reasonable value for the
    twobject-class-cache-size parameter: to cache every TWClass,
    for each snapshot count the number of 'BO' Types being used in
    BPDs and Services. This becomes more difficult when working
    with generic data types ('Any', 'map', or 'record'), as their
    number is finally determined during runtime. An advice is, to
    start with a cache-size of 5000 and vary this value during a
    set of performance tests.
    If this fix is applied in your product version and the symptoms
    an log statements appear, increase the cache by doubling
    current value and then measure performance.
    For more information, see ?Changing server properties in
    100Custom.xml?
    (http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm
    .wbpm.admin.doc/topics/changing_server_props.html) and ?The
    99Local.xml and 100Custom.xml configuration files?
    (http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm
    .wbpm.admin.doc/topics/managing_twks_config_settings.html).
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR51895:
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    2. Select APAR or SPR, enter JR51895, and click Continue.
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR51895

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-28

  • Closed date

    2015-06-16

  • Last modified date

    2017-02-10

  • 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

  • R801 PSY

       UP

  • R850 PSY

       UP

  • R855 PSY

       UP

[{"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.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 October 2021