Why would you do that? Keep the database open as a singleton instead.
----- Reply message ----- From: "noppanit" <noppani...@gmail.com> Date: Fri, Jul 15, 2011 7:00 pm Subject: [Neo4j] Best practice to avoid Unable to lock store error? To: "user@lists.neo4j.org" <user@lists.neo4j.org> Such as. Unable to lock store [/Users/xxx/db/neostore], this is usually caused by another Neo4j kernel already running in this JVM for this particular store I'm getting this error when the the user tries to insert into the database really fast (e.g, multiple clicks). The design that I use is to open and shutdown after each commit. So, sometime may be the database is not finish and the user clicks again. I think one way would be to disable the button after one click, but is there a better way to deal with that? -- View this message in context: http://neo4j-user-list.438527.n3.nabble.com/Best-practice-to-avoid-Unable-to-lock-store-error-tp3173592p3173592.html Sent from the Neo4J User List mailing list archive at Nabble.com. _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user