Vaccaro,
can you reliably reproduce this in a unit test? that would be very
helpful in doing something about it!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter
I can't reproduce this. I tried:
GraphDatabaseService db = new EmbeddedGraphDatabase( mydb );
IndexNode 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
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
Not currently, but I know there has been some discussions some time ago
about maybe adding such functionality (maybe automatically rolling back
ongoing transactions nicely in shutdown). I'm not fully aware of
implications that would have, but something like that could perhaps be good
to have.
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
5 matches
Mail list logo
