Direct links to fixes
APAR status
Closed as program error.
Error description
When you access information for a user, IBM Business Process Manager (BPM) loads the information into a user information cache. When the user is not yet available in the IBM BPM database, the user information is also initialized in the database. If a transaction fails that covers both the cache and database initialization, the database entry is rolled back, but the cache entry is not. As a result, the user is mismatched between the cache and the database.
Local fix
Manually reset the user information cache: 1. Log on to the Process Admin Console on the server where the problem occurred. Go to IBM BPM Admin > Manage Caches. 2. Locate the E§UserInfoCache entry. If you can't see it, click Refresh View and try again. 3. On the right side, in the Actions column, click Reset.
Problem summary
When the user is mismatched between the user information cache and the database, the user information cache holds references to users that are not in the database. Because the user information in the cache might be used for further database operations, a database transaction that follows the mismatch might fail with a constraint violation exception.
Problem conclusion
A fix that prevents the user information mismatch between the cache and the database. - is available for IBM BPM V8.5.5.0 - will be included in a future IBM BPM V8.5.6.0 cumulative fix After applying the fix, to prevent the transaction that loads the cache entry from using it, you can specify a period of time during which the cache entry is considered invalid and is not used if it has not been confirmed by at least one successful read from the database. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR53056: 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 JR53056, 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. Note: This behavior occurs in few environments. As a result, the specified period of time is set to 0, meaning that cache entries are always considered valid. Change this value only if you experience previously mentioned exceptions. To change the value, edit your 100Custom.xml file to contain an entry that is similar to the following entry: <server> <user-info-cache-block-period>120000 </user-info-cache-block-period> </server> The period is specified in ms (milliseconds). The recommended period is 120000 (2 minutes).
Temporary fix
Not applicable
Comments
APAR Information
APAR number
JR53056
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-08
Closed date
2015-11-17
Last modified date
2017-11-03
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
R855 PSY
UP
R856 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":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021