Hi Clark, I've converted your groovy code into java and run that in a unit test. As far as I can see all events trigger as they should.
What I'm worried about is the pattern that seems to be promoted here, namely to queue the event processing in an executor service. The transaction state of a transaction is local to the thread executing the transaction and simply handing over that state to another thread without any memory barriers isn't safe, i.e. it may yield unpredictable results. My advice to you is to simply scrap the executor service and execute whatever logic you need within the same thread that gets the beforeCommit/afterCommit calls. I'll also talk to Max about this, and update the javadocs. Please try this and report back with results. Best, Mattias -- 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/d/optout.
