Cannot log into JIRA after upgrade to 5.0.2 w/ Crowd Integration

[William Wells]

We just upgraded all of our Atlassian tools this past weekend and have run into a problem where users cannot log into JIRA. Previously we had the JIRA integration with Crowd, but we are seeing errors that seem to state that there's a stale connection within Crowd for JIRA. We had the same problem with Confluence and was able to rectify the problem by resetting the internal Confluence admin account, removing the Crowd integration and logging in locally and then re-establishing the integration with Crowd. The problem is, the initial JIRA (4.1.2) didn't seem to have a local admin account associated with it. So we tried to create a new one and then login locally the same way, but now we can't get in to setup the new Crowd integration.

The errors we are seeing are:

org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

While Confluence documents how to revert from Crowd to internal directory usage, JIRA's documentation doesn't reference this at all. We need help here badly as we're currently down on this JIRA instance.

[William Wells · Accepted solution]

it was actually a mispelling of the password in the crowd.properties. Pretty simple and stupid on my part. Thanks for helping.

[Aravind Chembeti]

There is a table "cwd_directory" in JIRA DB that will have all configured User Directories. By altering the column "directory_position" value in this table, one can bring JIRA back to its own internal directory for authentication

[Harry Chan]

Hi, which version of JIRA / Crowd are you now using? Are you bumping into https://jira.atlassian.com/browse/CWD-2703 that has now been fixed?