Hi Alexander,
I suggest you to manage transaction retry anyway, here is an example
http://orientdb.com/docs/last/Java-Multi-Threading.html#graph-api
Thanks
Luigi
2015-10-28 16:47 GMT+01:00 alexander anguiano :
> I just ran into this problem. In your response you say "reduce
> occurrences". S
I just ran into this problem. In your response you say "reduce
occurrences". So, shouldn't we catch the exception and try again in a loop
and give up after so many attempts? I thought i've seen some code that did
that at one point on this.
On Tuesday, September 15, 2015 at 10:53:37 AM UTC-5,
Hi,
OConcurrentModificationException happens when two clients try to update the
same record at the same time. It's a consequence of MVCC approach for
optimistic transactions (see http://orientdb.com/docs/last/Transactions.html
).
It also happens when you create edges, because also connected vertic
Hi all;
I am getting following error while running in distributed mode.
I tried sync and async replication and get the following error. Is there
anyone who experienced OConcurrentModificationException error.
Is this exception related to the following subject.
http://orientdb.com/docs/2.1/SQ
