Bug 1017458 - Intermittent OptimisticLockException on set project validation options
Intermittent OptimisticLockException on set project validation options
Status: CLOSED UPSTREAM
Product: Zanata
Classification: Community
Component: Component-Persistence (Show other bugs)
3.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Sean Flanigan
Zanata-QA Mailling List
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-09 19:43 EDT by Damian Jansen
Modified: 2015-07-30 21:14 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-30 21:14:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Test run log file (258.81 KB, text/plain)
2013-10-09 19:43 EDT, Damian Jansen
no flags Details

  None (edit)
Description Damian Jansen 2013-10-09 19:43:17 EDT
Created attachment 810206 [details]
Test run log file

Description of problem:
Sometimes selecting a validation option and pressing Update causes an exception.

Version-Release number of selected component (if applicable):
3.x

How reproducible:
Intermittent

Steps to Reproduce:
1. Sign in as admin
2. Go to project->version
3. Click Edit Version
4. Change a validation option
5. Press Update

Actual results:
In a small number of cases, StaleObjectStateException/OptimisticLockException occurs

Expected results:
No exception!

Additional info:
Attached log file
Comment 1 Damian Jansen 2014-07-28 01:57:44 EDT
Tested 3.5.0-SNAPSHOT (git-server-3.4.2-201-ge0afdde) - no longer an issue
Comment 2 Sean Flanigan 2015-04-16 23:44:19 EDT
I suspect this may have been caused by the accidental use of MyISAM for some tables.
Comment 3 Sean Flanigan 2015-04-17 02:38:30 EDT
On second thought, I have been seeing StaleObjectStateException in functional tests, which are probably not using MyISAM (MySQL 5.5.34 should default to InnoDB).  I think MyISAM problems must manifest differently.


org.zanata.feature.concurrentedit.ConcurrentAccessTest sometimes triggers these exceptions, especially if you run a few copies at once.

It's looking very much like a thread safety problem.  I'll see what I can do, at least for ConcurrentAccessTest.
Comment 4 Zanata Migrator 2015-07-30 21:14:27 EDT
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-373

Note You need to log in before you can comment on or make changes to this bug.