Resolving user mismatch between the user information cache and the database
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. If the user information in the cache is used for further database operations, a database transaction that follows the mismatch might fail with a constraint violation exception. To prevent this mismatch, you can add the user-info-cache-block-period configuration setting to the 100Custom.xml files. Using this setting, 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).
About this task
The problem of user information mismatch between the cache and the database only occurs in a few environments. As a result, the specified period of time is set to the default value of 0 milliseconds, which means that cache entries are always considered valid. You should only change this value if you experience exceptions, such as a SqlIntegrityConstraintViolationException exception in the SystemOut.log file that begins with the following lines:
com.lombardisoftware.client.delegate.BusinessDelegateException:
PreparedStatementCallback;
SQL [insert into LSW_USR_GRP_MEM_XREF (USER_ID, GROUP_ID) values (?, ?)];
Procedure
To add the configuration setting to the 100Custom.xml file, complete the following steps: