Seems that another thread is still running when I close the database, so nothing wrong with Neo4j, but with my code. :-(
Can I somehow force all running transactions (even when started from other threads) to finish? Am 29.03.2011 10:23, schrieb Mattias Persson: > I can't reproduce this. I tried: > > GraphDatabaseService db = new EmbeddedGraphDatabase( "mydb" ); > Index<Node> index = db.index().forNodes( "myindex" ); > Thread.sleep( 5000 ); > db.shutdown(); > > and no such message or recovery is displayed. Are you doing something else > in your simple example? > > 2011/3/28 Axel Morgner<[email protected]> > >> Good evening, >> >> lately I'm experiencing the following log message when closing the >> database, even if no write transaction was there between startup and >> shutdown. In my test, I even wait 5s before closing the database and >> another 5s before stopping the thread - same result. >> >> INFO: Close invoked with 1 running transaction(s) >> >> This always leads to an unclean shutdown, causing a long recovery period >> at next startup. Not sure, but I think it shows up since I upgraded to >> 1.3-M03, or using the new index framework (can't say exactly). >> >> I do shutdown the database with graphDb.shutdown() since I can think. >> >> Am I missing something? How can I avoid this behaviour? >> >> Greetings >> >> Axel >> >> >> >> _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user >> > > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
