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?)
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.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs