Re: Exception in thread main - error

2009-10-25 Thread Anshum
Hi Dhivya, It'd be a wise step to upgrade to a more recent lucene release. 2.9 (though that does not mean that the issue you encountered was because of that) would be ideal I'd say, but could also try 2.4. -- Anshum Gupta Naukri Labs! http://ai-cafe.blogspot.com The facts expressed here belong t

Exception in thread main - error

2009-10-25 Thread DHIVYA M
Sir/Mam,   Am M.Dhivya, learning about apache lucene [Java].   I have installed JDK-6 update 4 and NetBeans-6.5.1   I downloaded the lucene-1.9-final.zip file and followed the steps given in docs to run the demo.   The extracted lucene-1.9-final folder from the downloaded zip file is in D:\ and t

Re: IO exception during merge/optimize

2009-10-25 Thread Peter Keegan
The environment involves a lot of I/O from merge/optimize operations on multiple indexes (shards) on one server. I will try running the indexers in console mode, where I would expect to see all errors and exceptions. Peter On Sun, Oct 25, 2009 at 8:40 PM, Michael McCandless < luc...@mikemccandle

Re: IO exception during merge/optimize

2009-10-25 Thread Michael McCandless
Hmm, if you got no exception whatsoever, something more fundamental seems to be wrong w/ the error reporting when running as a windows service. Maybe make a simple Java test program that throws an exception and try to get that working? Mike On Sun, Oct 25, 2009 at 7:35 PM, Peter Keegan wrote: >

Re: IO exception during merge/optimize

2009-10-25 Thread Peter Keegan
>Did you get any traceback printed at all? no, only what I reported. >Did you see any BG thread exceptions on wherever your System.err is directed to? The jvm was running as a windows service, so output to System.err may have gone to the bit bucket. That's an interesting point, though. Peter On

Re: IO exception during merge/optimize

2009-10-25 Thread Michael McCandless
Hmm... Lucene tries to catch the original cause (from the BG thread doing the merge) and forward it to the main thread waiting for optimize to complete. Did you get any traceback printed at all? It should include one traceback into Lucene's optimized method, and then another (under "caused by") s