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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

SQL Error, Duplicate entry and HHH000315 in atlassian-crowd.log

In production we have the following triple log entries:

2014-08-05 00:26:38,514 ajp-bio-8009-exec-12 WARN [engine.jdbc.spi.SqlExceptionHelper] SQL Error: 1062, SQLState: 23000
2014-08-05 00:26:38,515 ajp-bio-8009-exec-12 ERROR [engine.jdbc.spi.SqlExceptionHelper] Duplicate entry 'F0Ed288GGEXEw8iDZrzMVQ00' for key 'uk_token_id_hash'
2014-08-05 00:26:38,515 ajp-bio-8009-exec-12 ERROR [jdbc.batch.internal.BatchingBatch] HHH000315: Exception executing batch [could not perform addBatch]
2014-08-05 00:46:28,325 ajp-bio-8009-exec-11 WARN [engine.jdbc.spi.SqlExceptionHelper] SQL Error: 1062, SQLState: 23000
2014-08-05 00:46:28,326 ajp-bio-8009-exec-11 ERROR [engine.jdbc.spi.SqlExceptionHelper] Duplicate entry 'F0Ed288GGEXEw8iDZrzMVQ00' for key 'uk_token_id_hash'
2014-08-05 00:46:28,326 ajp-bio-8009-exec-11 ERROR [jdbc.batch.internal.BatchingBatch] HHH000315: Exception executing batch [could not perform addBatch]

As you can see, it occurs at different times. sometimes one time a day sometimes two or more times.

A look at the DB table cwd_token shows a valid token for one of our applications. Here is the row (name of application is replaced by xxxxxxxx):

id      directory_id entity_name random_number       identifier_hash          random_hash              created_date        last_accessed_date  last_accessed_time duration 
------- ------------ ----------- ------------------- ------------------------ ------------------------ ------------------- ------------------- ------------------ -------- 
1580324 -1           XXXXXXXXXXX 4671076784804601889 F0Ed288GGEXEw8iDZrzMVQ00 PAT0NGQA9ZjaUHkef0vuOA00 2014-08-05 08:11:43 2014-08-05 08:11:43 1407224594771      60

We are using latest Crowd-Version 2.7.2 Build 626.

We don't have any functional problems so far, but these log entries makes me wonder.

3 answers

same problem with our setting: all latest versions: jira, confluence and crowd. some user got kicked out i.e. when they try to assign an issue - others when they do other actions. not really easy to find the root cause. JIRA shows me an incredible amount of user sessions and tomcat is spitting error on error.

Hi Jan, I just experienced the same error when setting domain attribute in Crowd setting from null to value '.srv' which is our internal DNS TLD for atlassian products. Do not know if it related to your problem tough.

Hi Mika,

if you mean the "SSO Domain" option in "General Options" of crowd adminstration: Yes, we have set this too. But we need to set it for cookie handling and security reasons.

Yes, that is what I mean. When I clear that setting and rebooted crowd: SQL problems disappeared and Crowd acted normally. No SSO tough, but authentication works from Jira / Confluence once again.

fyi: I am trying to get the SSO working between jira/confluence (all latest versions), but no luck yet :)

No ideas???

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events