IBM Support

JR58126: YOU EXPERIENCE PERFORMANCE ISSUES WHILE LOGGING IN

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

  • Logging in takes longer than expected and might fail if the user
    registry groups can't be retrieved when the server starts.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

  • Ensure all groups can be returned when the server starts.
    

Problem summary

  • IBM BPM replicates group names from the configured user registry
     into the product database when the server starts. For this
    purpose, IBM BPM uses a wildcard query to get all groups when
    the server starts. Some user registries do not return all groups
     (or any groups) in response to this query, for example if a
    configured maximum result size threshold is exceeded.
    
    Groups that have been replicated into the IBM BPM database but
    are not returned as part of the wildcard query when the server
    starts are marked deleted in the IBM BPM database and aren't
    added to the in-memory group cache.
    
    If these groups exist, this "marked as deleted" indicator in the
    database is incorrect. Moreover, if the groups are used for task
    assignment or observed as groups of a user when that user tries
    to log in, performance-expensive database queries occur, leading
    to poor login performance or even lock congestion.
    

Problem conclusion

  • A fix is included in IBM BPM V8.6 that prevents IBM BPM from
    marking security groups that exist in the IBM BPM table but are
    not returned from UserRegistry.getGroups API as inactive when
    the server starts. For example, UserRegistry.getGroups might not
     return all the groups that exist in an external user registry
    because either the VMM plug-in is partially implemented or the
    maximum result size threshold has been exceeded.
    
    To enable this feature, add the following lines to the
    100Custom.xml file after installing this fix:
    
    <common merge="mergeChildren">
     <security merge="mergeChildren">
      <mark-group-inactive-as-needed-in-start-up>false</mark-group-i
    nactive-as-needed-in-start-up>
     </security>
    </common>
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR58126

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-04

  • Closed date

    2017-09-08

  • Last modified date

    2017-10-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

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

Document Information

Modified date:
10 October 2017