Have you just upgraded to neo4j 1.3? In that case you need to
explicitly say that neo4j can upgrade your store, otherwise an
exception (wrapped in a TransactionFailureException) will be thrown at
startup. It would be helpful with the full stacktrace though, it
always is.
If it indeed is an
Hi All,
Just trying to get started with Neo4j, and I am seeing the issues reported
above. Initially I was getting the IllegalStateException: Unable to lock
store message, and now I'm getting the other message
TransactionFailureException: Could not create data source. The code
correctly created the
Hi,
Perhaps you're not shutting down the db after usage and have some other process
(or visualization like neoclipse in non-ro mode) running at the same datastore?
But as this seems to be blueprints related you should perhaps cross-post this
question on the tinkerpop/gremlin mailing list.
Hi Andrew,
Did you get a chance to see the solution posted by Andres?
http://lists.neo4j.org/pipermail/user/2010-September/005046.html
Check out the patched code in the gist he linked to in that email:
http://gist.github.com/594707
The problem with the example you were running was that the
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:
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
6 matches
Mail list logo
