look at my thread, maybe it helps you too.
On Friday, February 20, 2015 at 12:16:06 PM UTC+1, Bjorn Cintra wrote:
>
> Yeah, I figured yours was the same problem
>
> It seems that if I wait long enough, the connections get syncronized, and
> they see the same result. I can live with an eventual ty
Hi,
Could you create small test case so we should run it ?
On Fri, Feb 20, 2015 at 1:22 PM, Bjorn Cintra wrote:
> Oh, I also get OConcurrentModificationExceptions, wich seems a bit weird
> as well, since I am the only user, commiting 1 record at a time...
>
>
> On Friday, February 20, 2015 at 12
Oh, I also get OConcurrentModificationExceptions, wich seems a bit weird as
well, since I am the only user, commiting 1 record at a time...
On Friday, February 20, 2015 at 12:16:06 PM UTC+1, Bjorn Cintra wrote:
>
> Yeah, I figured yours was the same problem
>
> It seems that if I wait long enough
Yeah, I figured yours was the same problem
It seems that if I wait long enough, the connections get syncronized, and
they see the same result. I can live with an eventual type of consistency
(as I can mask it using client side JavaScript), but only if it takes <1
second to update.
The Gremlin
https://groups.google.com/forum/#!topic/orient-database/ERs4eaSGAjI
I have been debugging the same problem and it drives me crazy!
On Friday, February 20, 2015 at 11:20:09 AM UTC+1, Bjorn Cintra wrote:
>
> Hi
>
> My use case scenario is a web app, where the OrientGraphFactory is
> instanced as a
