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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo: Error occurred while saving build results. Reindex failed.

We are running Bamboo 5.9.1. on Windows and get the following error on some jobs :

Error occurred while saving build results. Reindex failed.

Caused by: java.sql.SQLException: Transaction (Process ID 126) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(
	at net.sourceforge.jtds.jdbc.TdsCore.getNextRow(
	at org.hibernate.loader.Loader.doQuery(
	at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(
	at org.hibernate.loader.Loader.loadCollectionBatch(

What is causing this condition?

It's a annoying since we have to manually restart build to resolve this condition. It typically seems to be generated on off the local agents.

2 answers

0 votes
Jaime S Atlassian Team Aug 10, 2015

Hi, Mark. 

I didn't get if this problem is happening in Bamboo or in the build you're running. That changes things.

If it's a problem in the build, you should check for any database transactions you're creating. Something there is causing a deadlock.

Either way, I found a KB for Confluence with a similar problem. Since it's a Confluence problem, it may not apply to this situation, but may help you better understand the problem.

Kind regards,
Jaime Kirch da Silveira
Atlassian Cloud Support

The error message is generated in the build plan. So what typically happens is that the build fails. I go to the related job and the error is shown in the Job Summary. See the attached screenshot. Since I am not creating database transaction, other then running builds, it must be Bamboo itself creating the deadlocks.

image2015-8-11 8:20:17.png


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

694 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you