Re: [Neo4j] threads on embeddedGraphDb

(inline response.) Am 28.09.2011 14:40, schrieb Peter Neubauer: > Hi there, > Neo4j in itself is thread safe, so you can pass it around as a > singleton and access it from different Java threads. knowing that it should work helped me to make it work. my mistake probably was to pass the instance

Re: [Neo4j] threads on embeddedGraphDb

Having multiple threads accessing a neo4j graph database concurrently is what it's built for. This looks to be an issue with a lucene index. java.nio.* is very sensitive to thread interrupts, but I've never seen this exception before. Are you using Thread.interrupt() or some library that might do t

Re: [Neo4j] threads on embeddedGraphDb

Hi there, Neo4j in itself is thread safe, so you can pass it around as a singleton and access it from different Java threads. The HighlyAvailableGraphDatabase for scaling over multiple machines is part of neo4j-enterprise, so you need to update your maven dependencies to change "community" for "en

[Neo4j] threads on embeddedGraphDb

hi, while i was not trying to use threads, everything went fine. now i need concurrent java threads to access the same (embedded?) graph database. neo4j-manual.pdf for 1.4.1 says in section 1.1.2. that i should use HighlyAvailableGraphDatabase, which is no longer there in 1.5.1 as it seems. i