Re: deadlock in indexing

2009-07-28 Thread Chengdu Huang
; > block you code for a while until the merge has finished. Can you >> > figure out if a merger-thread is running? The threads name should be >> > set to something like "Lucene Merge Thread #n" >> > >> > simon >> > >> > On Tue,

Re: deadlock in indexing

2009-07-28 Thread Chengdu Huang
is a backgroud merge going on while you try > to access the critical section ( you synchronized block) which could > block you code for a while until the merge has finished. Can you > figure out if a merger-thread is running? The threads name should be > set to something like &qu

Re: deadlock in indexing

2009-07-28 Thread Chengdu Huang
Thanks, Mike. Can you elaborate a bit more on why this would cause deadlock? Thanks. Chengdu On Tue, Jul 28, 2009 at 10:48 AM, Michael McCandless wrote: > This can in fact result in deadlock; you should sync on your own Object > instead. > > Mike > > On Tue, Jul 28, 2009 at

deadlock in indexing

2009-07-27 Thread Chengdu Huang
Hi, I have an application in which documents are added upon receiving a user request and a background thread is needed to remove old documents. I have an IndexWriter opened on a Directory that adds documents and commits but never closes. The background thread that removes documents uses the same