Bug 489370 - 2022: Object in use by another user when saving CTDE / TCE / TSE - editor content can not be saved
Summary: 2022: Object in use by another user when saving CTDE / TCE / TSE - editor con...
Status: CLOSED FIXED
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: 4.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
: 489372 (view as bug list)
Depends on:
Blocks: 489413
  Show dependency tree
 
Reported: 2016-03-10 11:22 EST by Daniel Tolgyesi CLA
Modified: 2016-05-19 03:37 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tolgyesi CLA 2016-03-10 11:22:17 EST 
You can reproduce the bug in the following way:

 - Create a new Central Test Data
 - Add a new parameter
 - Add a data value in Data Sets Editor
 - Save
 - Change this exist value to empty (do not delete the row)
 - Save
 - Create a new Test Suite
 - Write something into the existing empty Data Sets field
 - Save

 -> you got the following error message:

 2022: Object in use by another user
Comment 1 Daniel Tolgyesi CLA 2016-03-10 11:39:27 EST 
Perhaps the following bug is same:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=489372
Comment 2 Markus Tiede CLA 2016-03-11 03:43:32 EST 
*** Bug 489372 has been marked as a duplicate of this bug. ***
Comment 3 Markus Tiede CLA 2016-03-11 03:44:17 EST 
As discusses with AS.
Comment 4 Eclipse Genie CLA 2016-03-11 05:14:06 EST 
New Gerrit change created: https://git.eclipse.org/r/68198
Comment 6 Marvin Mueller CLA 2016-03-11 05:50:25 EST 
Somehow there are empty Strings in the TestDataCellPO from the master session. My assumption is that this leads, when creating a new Test Case/Suite to a change of the version of the TestDataCellPO. Since the version changed the editor has now an old version of the TestDataCellPO and the optimistic lock exception is thrown. I have checked this multiple times, and it is just writing new empty Strings into the databases.

We have decided not to use the @Version annotation for the TestDataCells which is used for the OptimisticLocking. This means the change done by our master session is not conflicting with the ones from the editor. 


I have also fixed two problems for a multi user environment which might lead to changed data even we get no locking for the Spec test cases(or for Central test data sets). This was happening when you tried to insert a new data set or move them. Than the data was inserted or moved even we had the message that we could not get locking for the Spec test case. This leads to an dirty editor and after saving this you had multiple unexpected errors.
Comment 7 Oliver Goetz CLA 2016-03-11 08:51:45 EST 
I am not able to reproduce this issue