The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error on rerunning failed builds since JDK 8 update

Jack Whelpton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 16, 2015

Hi,

We've recently updated our build images to version 8 of the JDK to ensure compatibility with Bamboo. Although builds are initiating fine, any attempt to rerun a build produces the following error:

Plan ... could not be started. org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; nested exception is org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

Do you have any idea how this could be resolved?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 16, 2015

Hello @Jack Whelpton,

Looks like you have https://jira.atlassian.com/browse/BAM-16332, current workaround is to decrease amount of storage used by artifacts to be less than 20 GB or switch to S3 artifact storage.

TAGS
AUG Leaders

Atlassian Community Events