-
Bug
-
Resolution: Fixed
-
Low
-
2.0.1, 2.0.3, 2.6.1
-
MySQL 5.X and Oracle 10.X
Crowd fails to add sequential LIST_INDEX numbers to table CWD_USER_CREDENTIAL_RECORD, setting the index to zero even if the user already has an entry, causing user deletion to fail.
ID, USER_ID, PASSWORD_HASH, LIST_INDEX "1","301015",7OXgRqJd6rgCcT0ZVGKYrYEJHA3CfIo9AuD79jbrSvIKIYt8p2fq0w7jR8UD+cCKoIKcou6md/gJQvXORbDArQ==,0 "2","301015",tG2gS45XeU2Brt3LgpS2/fd0uWx5DZ7fjxCLNHQlQ4NUg1wBRO0RVf3cWtG8kO5QY8M6I/niq4oY/tA+nmpJ7Q==,0 "3","301015",7OXgRqJd6rgCcT0ZVGKYrYEJHA3CfIo9AuD79jbrSvIKIYt8p2fq0w7jR8UD+cCKoIKcou6md/gJQvXORbDArQ==,0 "4","301015",tG2gS45XeU2Brt3LgpS2/fd0uWx5DZ7fjxCLNHQlQ4NUg1wBRO0RVf3cWtG8kO5QY8M6I/niq4oY/tA+nmpJ7Q==,0
2010-07-08 13:07:46,545 http-attuppaxxiam01%2F10.120.1.154-8095-16 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 2292, SQLState: 23000 2010-07-08 13:07:46,545 http-attuppaxxiam01%2F10.120.1.154-8095-16 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-02292: integrity constraint (CROWD_PROD_USER.FK_USER_CRED_USER) violated - child record found 2010-07-08 13:07:46,545 http-attuppaxxiam01%2F10.120.1.154-8095-16 ERROR [hibernate.event.def.AbstractFlushingEventListener] Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CWD-1979] Crowd fails to add sequential LIST_INDEX numbers to table CWD_USER_CREDENTIAL_RECORD
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 159601 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510926 ] | New: JAC Bug Workflow v3 [ 3365545 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392379 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510926 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 273692 ] | New: Simplified Crowd Development Workflow v2 [ 1392379 ] |
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 159601 ] | New: This issue links to "Page (Atlassian Documentation)" [ 159601 ] |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 159601 ] |
We're running 2.6.4, I've just used the SELECT query that Robert posted to check if we have any errant user records and it returns 0. However, Hercules is pointing me at this URL, suggesting that it has spotted something in the log file that could be related to this.
Any thoughts or comments?
| Remote Link | New: This issue links to "Wiki Page (Extranet)" [ 40258 ] |
I've merged the fix to 2_6_stable, it will ship in Crowd 2.6.2. The fix does not work retroactively, i.e., if you upgrade to Crowd 2.6.2 but your database is already inconsistent as a result of changing/resetting the password with an older version, you may have to manually edit the CWD_USER_CREDENTIAL_RECORD table to restore consistency.
Hi Philip,
Sometimes Hercules gets a bit ahead of himself and suggests things that aren't quite right. Since you're on 2.6.4 and this was resolved in 2.6.1, it's unlikely you're being affected by this exact issue.
If you're concerned about any functionality or would like to understand the errors that you're seeing in the logs, you can raise a ticket with our Support team and they can help you troubleshoot.
Kind regards,
Denise
Atlassian Support