This is a known issue. RemoteGraphDatabase was built as a tool for being able to connect to a running Graph Database and introspect the live state of the database without down the application.
The problem is in the RemoteGraphDatabase server that has issues with transaction handling under concurrent access. There are plans for fixing this issue, and also to work on making it possible to use RemoteGraphDatabase as an actual connector for implementing an application on (your use case). This will be done before the RemoteGraphDatabase component hits version 1.0, the current version is 0.7, but we have not decided on when this is going to be done though. Cheers, Tobias On Thu, Nov 11, 2010 at 2:33 PM, Anees Haider <[email protected]> wrote: > > > Hi, > > > > When I run the code with org.neo4j.kernel.EmbeddedGraphDatabase along with > org.neo4j.index.lucene.LuceneIndexService, it always executes magnificently > without even a single warning, but when I execute the code with > org.neo4j.remote.RemoteGraphDatabase along with > org.neo4j.remote.RemoteIndexService, it hardly run 1%-5% correctly, else > 95%-99% it gives org.neo4j.graphdb.NotInTransactionException exception. > > > > Please help me out, I will be grateful to you. > > > > > > > > Thanks and regards, > > Anees Haider > > > > > > P.S. We have to move from embedded graph database to remote graph database > because we have modular architecture (a lot of modules) and each module > (separate process) has to make separate connection to the neo4j database. > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Tobias Ivarsson <[email protected]> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
