Direct links to fixes
APAR status
Closed as program error.
Error description
When the new snapshot of a toolkit contains many business process definitions (BPDs) that are exposed to a team defined by a team retrieval service (TRS), upgrading the dependency of a process application to the new snapshot might be time consuming. Occasionally, you might see an exception like the following exception: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO LSW_LOCK (LOCK_ID, DESCRIPTION) VALUES (?,?)]; ORA-00001: unique constraint (BPMUSER.LSWC_LOCK) violated ; nested exception is com.ibm.websphere.ce.cm.DuplicateKeyException: ORA-00001: unique constraint (BPMUSER.LSWC_LOCK) violated at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTransla tor.translate(SQLErrorCodeSQLExceptionTranslator.java:292) at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate. java:607) at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.j ava:792) at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.j ava:850) at com.lombardisoftware.utility.db.SynchronizationWithDB.createSync hronizationLock(SynchronizationWithDB.java:88) at com.lombardisoftware.utility.db.SynchronizationWithDBInCurrentTX .synchronize(SynchronizationWithDBInCurrentTX.java:29) at com.lombardisoftware.server.ejb.persistence.dao.UserGroupDAO.loc kGroup(UserGroupDAO.java:494) at com.lombardisoftware.server.ejb.persistence.dao.UserGroupMemberD AO.insert(UserGroupMemberDAO.java:86) at com.lombardisoftware.server.ejb.security.InternalGroupsCore.addU serToInternalGroup(InternalGroupsCore.java:204) at com.lombardisoftware.server.ejb.security.InternalGroupsCore.addU serToInternalGroup(InternalGroupsCore.java:184)
Local fix
Problem summary
The internal evaluation that determines whether a user must be added to a user group constantly queries the database, which takes a lot of time. Furthermore, when the user is added to a user group, the user group is locked by inserting a row into the LSW_LOCK database table. This action occasionally leads to a unique constraint violation because the value for the key column is generated ambiguously.
Problem conclusion
A fix is available for IBM BPM V8.5.6 cumulative fix 2 (http://www.ibm.com/support/docview.wss?uid=swg24041303) and the problem is fixed in cumulative fix 8.5.7.0 2017.12, that uses an internal user-group-membership cache to determine whether a user must be added to a group, thereby speeding the process. When the user is added to a user group and the user group gets locked by inserting a row into the LSW_LOCK table, the value for the key column is generated unambiguously.
Temporary fix
Comments
APAR Information
APAR number
JR56649
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
856
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-14
Closed date
2017-04-10
Last modified date
2017-04-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
R856 PSY
UP
R857 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":"856","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 October 2021