..
>> >>>> >
>> >>>> > Thread [pool-3-thread-5] (Suspended)
>> >>>> > IndexWriter.doWait() line: 4494
>> >>>> > IndexWriter.optimize(int, boolean) line: 2283
>> >>>> > Ind
>PersistenceJobConsumer.consume() line: 46
> >>>> >PersistenceJobConsumer.run() line: 67
> >>>> >Executors$RunnableAdapter.call() line: 441
> >>>> >FutureTask$Sync.innerRun() line: 303
> >>>> >FutureT
ThreadPoolExecutor$Worker.run() line: 908
>>>> > Thread.run() line: 619
>>>> >
>>>> > thanks,
>>>> >
>>>> > C>T>
>>>> >
>>>> > On Fri, Oct 16, 2009 at 1:58 PM, Michael McCandless <
>&
>> Is it possible to get the stack trace of the thrown exception when the
>>> >> thread was interrupted? Maybe indeed something in IW isn't cleaning
>>> >> up its state on being interrupted.
>>> >>
>>> >> Mike
>>> >>
gt;> >> > consumer object itself).
>> >> > The thread is waiting at IndexWriter.doWait(). What might cuase
>> this?
>> >> >
>> >> > thanks -
>> >> >
>> >> > C>T>
>> >> >
>> >&g
t; > C>T>
> >> >
> >> > On Fri, Oct 16, 2009 at 12:58 PM, Uwe Schindler
> wrote:
> >> >
> >> >> Do you use the IndexWriter as mutex in a synchronized() block? This
> is
> >> not
> >> >> supported and may hang.
M, Uwe Schindler wrote:
>> >
>> >> Do you use the IndexWriter as mutex in a synchronized() block? This is
>> not
>> >> supported and may hang. Never lock on IndexWriter instances. IndexWriter
>> >> itself is thread safe.
>> >>
>> &g
IndexWriter instances. IndexWriter
> >> itself is thread safe.
> >>
> >> -
> >> Uwe Schindler
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >> > -Original M
e-
>> > From: Christopher Tignor [mailto:ctig...@thinkmap.com]
>> > Sent: Friday, October 16, 2009 6:50 PM
>> > To: java-user
>> > Subject: IndexWriter optimize() deadlock
>> >
>> > Hello,
>> >
>> > I am trying to track down the
e 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Christopher Tignor [mailto:ctig...@thinkmap.com]
> > Sent: Friday, October 16, 2009 6:50 PM
> > To: java-user
> > Subject: IndexWriter optimize() deadloc
nal Message-
> From: Christopher Tignor [mailto:ctig...@thinkmap.com]
> Sent: Friday, October 16, 2009 6:50 PM
> To: java-user
> Subject: IndexWriter optimize() deadlock
>
> Hello,
>
> I am trying to track down the cause of my code hanging on calling
> IndexWriter.opt
Hello,
I am trying to track down the cause of my code hanging on calling
IndexWriter.optimize() at its doWait() method.
It appears, thus that it is watiing on other merges to happen which is a bit
confusing to me:
My application is a simple producer consumer model where documents are added
to a q
12 matches
Mail list logo
