Eclipse Community Forums: EMF » [CDO] Attempt by Transaction[2:8] to modify historical revision

Home » Modeling » EMF » [CDO] Attempt by Transaction[2:8] to modify historical revision

[CDO] Attempt by Transaction[2:8] to modify historical revision [message #1753853]

Fri, 10 February 2017 12:31

Eclipse User

This is the situation:
Two different transactions concurrently add new EObjects (each one) to the same Resource.

Exception:

org.eclipse.emf.cdo.util.CommitConflictException: Attempt by Transaction[2:8] to modify historical revision: CDORevisionDelta[CDOResource@OID9:0v1 --> [CDOFeatureDelta[contents, LIST, originSize=0, list=[CDOFeatureDelta[contents, ADD, value=oid1, index=0]]]]]
	at org.eclipse.emf.internal.cdo.transaction.CDOSingleTransactionStrategyImpl.commit(CDOSingleTransactionStrategyImpl.java:77)
	at org.eclipse.emf.internal.cdo.transaction.CDOTransactionImpl.commitSynced(CDOTransactionImpl.java:1610)
	at org.eclipse.emf.internal.cdo.transaction.CDOTransactionImpl.commit(CDOTransactionImpl.java:1573)
	at org.eclipse.emf.internal.cdo.transaction.CDOTransactionImpl.commit(CDOTransactionImpl.java:1540)

This even occurs if I add CDOMergingConflictResolver to the transaction's conflict resolvers.
Should CDOMergingConflictResolver handle this case? If not, what do I have to provide to handle this "simple" conflict?

Thanks.

Re: [CDO] Attempt by Transaction[2:8] to modify historical revision [message #1753961 is a reply to message #1753853]

Mon, 13 February 2017 07:40

Eclipse User

Conflict resolvers reduce the potential of conflicts a lot, but they can't eliminate the potential completely. Only explicit locks can do that.

Previous Topic:	Merging metamodels
Next Topic:	[XCORE] Warning "The feature is bidirectional reference."

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 14 08:55:26 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter