Hi Tai, We need code to verify that you do everything correctly and that is bug in the system.
On Thu, Mar 10, 2016 at 8:24 PM Tai Hu <[email protected]> wrote: > Hi, > I am using latest 2.2.0-beta in a multithread environment and > encountered a weird issue, which I never had in 2.1.x version. (I am using > embeded OrientDB) > > 1. Thread A created a vertex A in OrientDB and committed. > 2. Thread B starts and try to query Vertex A, I will always get a Vertex > #<id> did not find exception (Thread B's transaction is started after > Thread A transaction committed). > 3. If I restart the application, vertex A is there in the database and > visible to all threads. > > Also I noticed that with verion 2.2.0-beta, on Windows almost every time > when I start my application, I will get a OrientDB index engine is > corrupted and need to rebuild error. But same error never happen on a Mac. > > Thanks, > > Tai > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Best regards, Andrey Lomakin, R&D lead. OrientDB Ltd twitter:@Andrey_Lomakin linkedin:https://ua.linkedin.com/in/andreylomakin -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
