Direct links to fixes
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products
Closed as program error.
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.
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.
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.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
24 August 2015