SOLR 4 / Tomcat Startup Error: java.lang.NoClassDefFoundError: org/apache/lucene/codecs/sep/IntStreamFactory

[vybe3142 <vy...@gmail.com>]

I could well be doing something wrong here, but so far I haven't figured it
out. I currently  run SOLR 4 BETA  / multicore and I was investigating
migrating to SOLR 4.0 (on my workstation).

I've even backed out my custom schema and solrconfig so I'm running as close
to original as possible with no custom handlers etc.

Any idea which jar I'm missing? I should be referencing all the jars
provided in the 4.0 tar file.

Thanks






--
View this message in context: http://lucene.472066.n3.nabble.com/SOLR-4-Tomcat-Startup-Error-java-lang-NoClassDefFoundError-org-apache-lucene-codecs-sep-IntStreamFacy-tp4016853.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: SOLR 4 / Tomcat Startup Error: java.lang.NoClassDefFoundError: org/apache/lucene/codecs/sep/IntStreamFactory

[Shawn Heisey <so...@elyograg.org>]

On 10/29/2012 5:28 PM, vybe3142 wrote:
> I could well be doing something wrong here, but so far I haven't figured it
> out. I currently  run SOLR 4 BETA  / multicore and I was investigating
> migrating to SOLR 4.0 (on my workstation).
>
> I've even backed out my custom schema and solrconfig so I'm running as close
> to original as possible with no custom handlers etc.
>
> Any idea which jar I'm missing? I should be referencing all the jars
> provided in the 4.0 tar file.

That particular class is part of lucene-codecs.  This file is not part 
of the Solr 4.0 binary release, and is not generated by "ant dist" in 
the source tree under solr/.  The only way I know of to get it from the 
source is by doing "ant generate-maven-artifacts" in the root of the 
source tree.

You should not need it, however, unless you are attempting to change 
lucene codecs (postingsFormat) in your schema.  If this is what you are 
trying to do, you can ignore the following:

I am guessing that you still have leftover bits in your tomcat's 
deployment directory from the 4.0 beta .war file.  If that's the case, 
you can fix it by stopping tomcat, erasing everything in the deployment 
directory, and starting tomcat back up.  It will redeploy from the new 
.war file.

Thanks,
Shawn