Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

HibernateOptimisticLockingFailureException when renaming a single requirement

Fix versions

None

Priority

Description

I'm currently renaming a bunch of requirements (one by one). From time to time (not reproducable), I get this error:

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 StaleStateException Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

In order to be quicker in renaming many requirements, I'm working in two tabs in parallel, could that produce the issue?
I only get it every 8-10 requirements. When I then try again with the exact same keys (old -> new), it works.

Attachments

1
  • 06 Dec 2019, 01:49 PM

Activity

Show:

Former userDecember 9, 2019 at 7:35 AM
Edited

Hi Adrien, we are running fully on MSSQL. The requirements were not linked to the same issue; but what is suspicious that the error always happened when scanning through the Confluence pages.

P.S.: I think once the multi-rename becomes more useable (see RY-513), then this bug will be less relevant as then I would not need to single-rename in parallel.

Adrien RagotDecember 6, 2019 at 4:43 PM

Hi Michael,

I have never seen such an issue.

Google suggests that this errors happens in MySQL, is it your database?

We've already tried with jobs in parallel, but only on separate issues. Are your requirements linked to the same issue?

Thank you,
Adrien

Details

Assignee

Reporter

Components

Affects versions

Requirement Yogi

Created December 6, 2019 at 1:50 PM
Updated December 9, 2019 at 7:36 AM
Configure