Direct links to fixes
APAR status
Closed as program error.
Error description
This is a performance issue while using the BPM product. A cache entry that contains user details is found only when the user name exactly matches the user name stored in the IBM Business Process Manager (BPM) database. When you use an external authentication system, the user name asserted by the external system for IBM BPM does not have to exactly match the user name stored in the user registry. When you first log in, the user name gets inserted in the IBM BPM database with the user name from the external system. Upon subsequent logins with varying capitalization for the user name, the user name that external system generates and IBM BPM uses differs from the initially used user name. In such cases, an available cache entry is not found. As a result, the system tries to repeatedly access the IBM BPM database to get the user details and performance degrades. The query used to get the user details is select t0.USER_ID, t0.USER_NAME, t0.FULL_NAME, t0.PROVIDER from LSW_USR_XREF t0 where UPPER(USER_NAME) = :1] Number of executions = 328103 Total execution time (sec.microsec)= 1252.108524 Statement text = select t0.USER_ID,t0.USER_NAME,t0.FULL_NAME,t0.PROVIDER from LSW_USR_XREF t0 where UPPER(USER_NAME) = ? This issue may occur when a third party service is used for single sign on (SSO). IDENTIFY THIS ISSUE With this trace WLE.*=all:WAS.clientinfopluslogging=all the traces will have this statement repeated thousands of times. JdbcTemplate 1 org.springframework.jdbc.core.JdbcTemplate execute Executing prepared SQL statement [select t0.USER_ID,t0.USER_NAME,t0.FULL_NAME,t0.PROVIDER from LSW_USR_XREF t0 where UPPER(USER_NAME) = ?] When a user first authenticates or is synced to BPM meta data about their user name is stored in LSW_USR_XREF. For this example, let us suppose John Smith first logs in with the user name of 'JSMITH' in all upper case (capitals). this is recorded in the user_name column. On subsequent logins he user 'jsmith' as lower case. What can happen is when the system needs the username, the cached copy from login 'jsmith' is a mismatch to the XREF entry of "JSMITH" so what happens is the SQL call for UPPER is called thousands of times while using a coach. If the same user logs in as 'JSMITH' the calls to the coach are very fast. Apply this fix to resolve this issue
Local fix
Users can login with the exact same case as is recorded in the LSW_USR_XREF table.
Problem summary
No additional information is available.
Problem conclusion
A fix is available for IBM BPM V8.5.0.1 that makes sure that the user details cache can be read by using any user name that the user registry accepts, without imposing additional restrictions on the capitalization of the user name. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR51631: 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 JR51631, 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
JR51631
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-24
Closed date
2015-01-12
Last modified date
2017-08-31
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
R850 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021