Hi Guys, I'm not sure if this issue was sorted but if it helps I found that this error happens to me when I use a 32 bit JVM and not when I use a 64 bit JVM of the same version. There's still some undeterministic behavior associated with this because it'll also only happen when I run 2 junit test cases (one after the other) where each test creates a separate instance of an embedded graph database (named separately etc). The second one that runs is the one that continuously fails to "clean up" after itself by not being able to drop constraints. I thought it might have something to do with the first test case creating a separate instance of a graph database but I can't see how because they're (seemingly) totally separate. I'm not sure if that helps or makes much sense.
The java version I'm using is 1.7.0_55. Thanks! Jim On Sunday, March 30, 2014 5:42:35 AM UTC-4, Rio Eduardo wrote: > > Oh ok but, when I tried to drop it, I already made sure the constraint was > online. > > On Sunday, March 30, 2014 4:23:23 PM UTC+7, Michael Hunger wrote: >> >> Could it be that the constraint was not yet online when you tried to drop >> it? I.e. it was still building? >> >> It seems lucene was still writing to the backing files. >> >> Caused by: java.io.IOException: Cannot delete C:\Users\Olivia >> Stella\Documents\Neo4j\DB_1000\schema\index\lucene\3\_0.fdt >> >> >> >> >> On Sun, Mar 30, 2014 at 10:45 AM, Rio Eduardo <[email protected]> >> wrote: >> >>> Oh ok, here is my graph.db/messages.log. Oh yeah I almost forgot to tell >>> and it's successful when I create/drop constraint in web ui browser but not >>> in Neo4j Shell. >>> >>> Thank you. >>> >>> >>> On Sunday, March 30, 2014 3:16:20 PM UTC+7, Michael Hunger wrote: >>> >>>> Something went wrong there. >>>> >>>> Can you share your graph.db/messages.log file to see if we can find out >>>> the reason? >>>> >>>> Your create/drop constraint syntax is correct. >>>> >>>> >>>> On Sun, Mar 30, 2014 at 7:52 AM, Rio Eduardo <[email protected]> >>>> wrote: >>>> >>>>> I create constraint in Neo4j Shell(2.0.1) with this syntax => CREATE >>>>> CONSTRAINT ON(U:User) ASSERT U.user_id is UNIQUE; >>>>> And can see the schema with this syntax => schema ls -l :User >>>>> >>>>> but when I want to drop contraint with this syntax => DROP CONSTRAINT >>>>> ON(U:User) ASSERT U.user_id is UNIQUE; >>>>> it returns error result => SystemException: TM has encountered some >>>>> problem, please perform necessary action (tx recovery/restart) >>>>> And when I want to see the scema with this syntax => schema ls -l :User >>>>> it returns error result too => SystemException: TM has encountered >>>>> some problem, please perform necessary action (tx recovery/restart) >>>>> >>>>> And when I restart my neo4j, and see the schema, suddenly there is no >>>>> indexes and constraints that I already created before. >>>>> >>>>> so, What happened to my neo4j actually? and how to solve this problem? >>>>> and how to drop constraint with this syntax => DROP CONSTRAINT ON(U:User) >>>>> ASSERT U.user_id is UNIQUE;? >>>>> >>>>> Thank you. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Neo4j" 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. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Neo4j" 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. >>> >> >> -- You received this message because you are subscribed to the Google Groups "Neo4j" 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.
