IBM Support

JR53674: GROUP SYNCHRONIZATION FAILS FOR EXISTING GROUPS AFTER TRAILING BLANKS (WHITE SPACES) ARE REMOVED FROM THE USER REPOSITORY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you have groups in your user repository (for example, LDAP)
    that have trailing blanks (white spaces) in the group name and
    you remove the trailing spaces later, the group synchronization
    fails when the server starts. In the SystemOut.log file, you see
    the following message:
    
    wle_security  I com.lombardisoftware.server.core.GroupCore
    saveUserGroups : Error saving user Groups
    
    Additionally, a FFDC that contains an exception like the
    following exception is generated:
    
    SQL STATE:  23000
    ERROR CODE: 2601
    java.sql.BatchUpdateException: Cannot insert duplicate key row
    in object
    'LSW_USR_GRP_XREF' with unique index 'LSWC_GXREF_UQ'. The
    duplicate
    key value is (<groupname>).
    
    <groupname> is the name of the group with the trailing blanks.
    

Local fix

Problem summary

  • The group synchronization logic compares group names from the
    database with the set of group names in the user repository.
    This comparison is strict, meaning that it does not abstract the
    group  names from those with trailing white spaces. Therefore,
    an attempt is made to insert the new group name (without white
    spaces) into the IBM BPM database. This attempt fails because
    the database recognizes the new group name as being equivalent
    to the existing group name, including the white spaces.
    Inserting two equivalent group names fails because of a database
    constraint defined by IBM BPM.
    

Problem conclusion

  • A fix is/will be available for IBM BPM that ensures that
    the comparison logic is the same in IBM BPM and SQL during group
    synchronization.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53674:
    
    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 JR53674 , 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

    JR53674

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-30

  • Closed date

    2015-08-24

  • Last modified date

    2015-08-24

  • 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

  • R856 PSY

       UP

[{"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":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 August 2015