Is it possible that you somehow have some problem with jars and classpath? I'm wondering because this problem really seems odd, and you've eliminated a bunch of possibilities. I'm wondering if you've somehow gotten some old jars mixed in the bunch.
Or, alternately, what about re-installing Solr on the theory that somehow you got a bad download and/or files (i.e. the Solr jar files) got corrupted, your disk has a bad spot or..... Really clutching at straws here.... Erick On Mon, Jun 18, 2012 at 3:44 AM, Rok Rejc <rokrej...@gmail.com> wrote: > Hi all, > > during the last days, I have create solr instance on a windows environment > - same Solr as on the linux machine (solr 4.0 from 9th June 2012), same > solr configurations, Tomcat 6, Java 6u23. > I have also upgraded Java on the linux machine (1.7.0_05-b05 from Oracle). > > Import and optimize on the windows machine worked without any issue, but on > the linux machine optimize fails with the same exception: > > Caused by: java.io.IOException: Invalid vInt detected (too many bits) > at > org.apache.lucene.store.BufferedIndexInput.readVInt(BufferedIndexInput.java:217) > ... > > after that I have also change directory factory (on the linux machine) to > SimpleFSDirectoryFactory. I have reindexed all the documents and again run > the optimize - it fails again with the same expcetion. > > In the next steps I could maybe do partial insertions (which will be a > painful process), but after that I'm out of ideas (and out of time for > experimenting). > > Many thanks for further suggestions. > > Rok > > > > On Wed, Jun 13, 2012 at 1:31 PM, Robert Muir <rcm...@gmail.com> wrote: > >> On Thu, Jun 7, 2012 at 5:50 AM, Rok Rejc <rokrej...@gmail.com> wrote: >> > - java.runtime.nameOpenJDK Runtime Environment >> > - java.runtime.version1.6.0_22-b22 >> ... >> > >> > As far as I see from the JIRA issue I have the patch attached (as >> mentioned >> > I have a trunk version from May 12). Any ideas? >> > >> >> its not guaranteed that the patch will workaround all hotspot bugs >> related to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5091921 >> >> Since you can reproduce, is it possible for you to re-test the >> scenario with a newer JVM (e.g. 1.7.0_04) just to rule that out? >> >> -- >> lucidimagination.com >>
