Re: [Neo] Lucene Index Corruption?

2009-12-11 Thread Johan Svensson
Hi, I do think the best solution is to make NeoService.shutdown() (either by default or parameter/config) do the following: 1) block or throw exception for threads trying to start a new transaction 2) rollback all transactions that are not yet in committing state 3) wait for transactions that

Re: [Neo] Lucene Index Corruption?

2009-12-10 Thread Johan Svensson
Hi Adam, On Wed, Dec 9, 2009 at 4:37 PM, Adam Rabung adamrab...@gmail.com wrote: 1. This iterator will just prevent duplicates from being returned from the iterator?  If there's a condition (bug in my code) that causes shutdown w/ open transactions, will the Lucene indexes continue to double

Re: [Neo] Lucene Index Corruption?

2009-12-10 Thread Adam Rabung
Hi, Thanks for all of the information. Of course the #1 solution to this problem is to ensure all transactions are closed before shutdown is called. I am trying to implement some kind of failsafe in the case that some unforeseen problem/bug causes transactions to remain open. What do you think