Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,354
Community Members
 
Community Events
176
Community Groups

Unable to authenticate JIRA 5.0.2 with Crowd 2.4.1 after upgrade

We recently performed an upgrade from JIRA 4.1.2 and Crowd 2.0.7 to 5.0.2 and 2.4.1 respectively. After the upgrade, we are unable to authenticate users against Crowd and are receiving the following error in the Crowd logs:

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

We also upgraded out Confluence from 3.3.3 to 4.1.7 and found a similar issue where it seemed that Confluence was holding onto an old stale state with the older version of Crowd. To resolve that issue, we reset the Confluence internal directory password for the admin account and went through the steps to re-establish a Crowd integration.

We didn't seem to have an admin account in our JIRA instance so we followed the steps in https://confluence.atlassian.com/display/JIRA050/Retrieving+the+JIRA+Administrator but that didn't seem to help us any and we still cannot login (locally nor crowd related). We've been looking through all of the knowledge base, documentation, submitted to the Ask Atlassian forums, but we're stumped at this point.

2 answers

1 accepted

0 votes
Answer accepted

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

0 votes
MatthewC Rising Star Sep 25, 2012

Assuming you have a valid licence, I'd raise a support call with Atlassian? http://support.atlassian.com

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events