Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×After upgrading Crowd 2.0.7 to 2.5.1 yesterday I've seen a SQL error a couple times in atlassian-crowd.log. See attached stack trace. (actually seen it twice, ~24hrs between.)
Looks like a uniqe constraint violation in table cwd_token.
Can this be fixed easily in a nice way?
(Or hacker-style: Stop crowd & clear table?)
(crowdStack.txt)
Otherwise Crowd seems to be working fine after the upgrade. But it would be nice to not have this error in logfile.
I would suggest the SQL approach, unless you can find the row in question that is causing the violation, and removing just that record.
Removing all tokens would logout all sessions for all users + applications currently using Crowd for authentication.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.