Account lockout updates

I'm seeing many logs saying that the AccountLockoutManager could update last login:

2023-07-07 23:16:10,031 qtp1459794865-130  WARN AccountLockoutManager:104 - Could not update last login for matija.obreza@croptrust.org: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update acl_sid set active=?, version=?, lastModifiedBy=?, lastModifiedDate=?, principal=?, sid=? where id=? and version=?; nested exception is org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update acl_sid set active=?, version=?, lastModifiedBy=?, lastModifiedDate=?, principal=?, sid=? where id=? and version=?
2023-07-07 23:16:10,411 qtp1459794865-132  WARN AccountLockoutManager:104 - Could not update last login for matija.obreza@croptrust.org: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update acl_sid set active=?, version=?, lastModifiedBy=?, lastModifiedDate=?, principal=?, sid=? where id=? and version=?; nested exception is org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update acl_sid set active=?, version=?, lastModifiedBy=?, lastModifiedDate=?, principal=?, sid=? where id=? and version=?

Please check and update the updating logic.