Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sequential document updates from different connections yields conncurrent modification exception [moved] #75

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Sequential document updates from different connections yields conncurrent modification exception [moved] #75

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 75 moved from a Google Code project.
Added by 2010-07-24T09:34:43.000Z by lavikain...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-Medium, v0.9.21

Original description

When same document is modified from different connections, even if they are in same thread and proper transaction management is used, sequential updates yields concurrent modification exception.

I have created a test case (against version 0.9.20) that has four tests that will show what is happening.
@lvca lvca closed this as completed Dec 10, 2012
@henryzhao81 henryzhao81 mentioned this issue May 15, 2015
Closed
lvca added a commit that referenced this issue Oct 15, 2015
@lvca
Merge pull request #75 from bmcgavin/master
9733a8e 
Don't try to create a Vertex if the value in the import data is null
@ashkumar ashkumar mentioned this issue Jan 19, 2017
Closed
4 tasks
@CyprienGottstein CyprienGottstein mentioned this issue May 29, 2018
Closed
@StevenHeven StevenHeven mentioned this issue Aug 12, 2019
Closed
@jamieb22 jamieb22 mentioned this issue Nov 11, 2019
Closed
@madmac2501 madmac2501 mentioned this issue Jun 7, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lvca