It automatically starts transactions. Try to do g.commit() before you shut down.
Michael Am 18.01.2014 um 03:18 schrieb Jack Jones <[email protected]>: > Hmm, I'm actually not reading or writing anything, just starting up and > shutting down. I am using it with TinkerPop Blueprints 2.5 though, I wonder > if that's doing something with a transaction. Let me look into that a bit. > > On Friday, January 17, 2014 8:33:18 PM UTC-5, Michael Hunger wrote: > Jack, > > you have still open/dangling transactions, if you close them correctly it > will shut down instantly. > > Michael > > Am 18.01.2014 um 01:55 schrieb Jack Jones <[email protected]>: > >> Hi there, >> >> I've noticed since I started using 1.9.5 and continuing with 2.0, shutting >> down the database takes a very long time. Looking at the messages.log file >> shows that the delay seems to occur between the "Database is now >> unavailable" and the "GC Monitor stopped" messages, with a delay of exactly >> 20 seconds. I'm using it embedded. I don't see any settings in the kernel >> configuration with a setting of 20s. Is this a known issue or expected >> behavior? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Neo4j" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
