The cause of this problem (for the OverlappingFileLockException) is that there's another Neo4j kernel instance already running withing the same JVM for that particular store. I also improved the exception to say that.
2010/9/23 Andrew Grealy <iag...@yahoo.com> > Hi All, > > I have been on the learning path for Neo4J. I came across a problem people > are experiencing. > > If you write groovy scripts to learn how to use Noe4j, then if they bomb > out you are left with the 'unable to lock store problem'. > > I was playing with groovy code from: > http://groovyconsole.appspot.com/script/245001 > (To reproduce the problem just make a bug, such as comment out the > tx.success() line then re-run again) > > I then tried doing the same thing in Java, to confirm Neo4J isn't flakey. > Neo4J was rock solid. This may explain why all the people answering guys > messages on this problem says it because you have two applications accessing > the system. (Which I can tell you only had one groovy script running at a > time.) > > I would like to make a suggestion have a special startup mode, that can > clear the state on startup. (Getting to work again, was painful). In > development this would be useful, it would be an over-ride and not normal > operation > > cheers, > Andrew > > > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
