Robert Haschart <[EMAIL PROTECTED]> wrote: > To answer your questions: I completely deleted the index each time > before retesting. and the java command as shown by "ps" does show -Xbatch. > The program is running on: > > uname -a > Linux lab8.betech.virginia.edu 2.6.18-53.1.14.el5 #1 SMP Tue Feb 19 > 07:18:21 EST 2008 i686 i686 i386 GNU/Linux > > more /etc/redhat-release > Red Hat Enterprise Linux Server release 5.1 (Tikanga) > > after downgrading from the originally reported version of java: Java(TM) > SE Runtime Environment (build 1.6.0_05-b13) > to this one: > > java -version > java version "1.6.0_02" > Java(TM) SE Runtime Environment (build 1.6.0_02-b05) > Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode) > > the indexing run sucessfully completed processing all 112 record chunks! > Yea! > (with -Xbatch on the command line, I didn't try with the 1.6.0_02 java > without -Xbatch)
OK, that's good and bad news. Good in that this still appears to be a JVM issue (scary, really) since downgrading to 1.6.0_02 resolves it. Bad in that -Xbatch is not always a viable workaround. But at least you have a way forward... > So at this point it looks like the problem is in my marc-8 to utf-8 > translation code. I'll look into this possibility further. OK. Let me know if this seems to come back to a Lucene issue! Mike
