I'm still not exactly clear on why this is the case, but the problem
turned out to be that the extra libs needed to be in my tomcat app's
WEB-INF/lib directory, rather than ${solrhome]/lib. I don't really
understand the distinction between the two, especially since Solr was
reporting that it was loading the libs found in ${solrhome}/lib.
At any rate, problem solved.
On Mon, Apr 9, 2012 at 1:36 PM, Chris Hostetter
<hossman_luc...@fucit.org> wrote:
>
> : Further info: I can make this work if I stay out of tomcat -- I
> : download a fresh solr binary distro, copy those five JARs from 'dist'
> : and 'contrib' into example/solr/lib/, copy my solrconfig.xml and
> : schema.xml, and run 'java -jar start.jar', and it works fine. But
> : trying to add those same JARs to my tomcat instance's solrhome/lib
> : doesn't work. Any ideas how to troubleshoot?
>
> is there anything else about how you have tomicat+solr configured that
> might be causing tomcat to load *any* solr or lucene jars directly,
> instead of letting the solr.war file load them from your solr home dir?
> did you change anything about tomcat's classpath? did you copy any jars
> anywhere other then your solrhome/lib dir?
>
> these kinds of "classloader hell" errors can happen if a parent
> classloader has already loaded some class that depends on (or is depended
> on by) a another class loaded by the solr war.
>
>
> -Hoss
