: An important factor in the instruction is that Tomcat must
: be started from the directory under which the solr directory
: (copied from the exmaple) exists. That is, Solr runs only
: if Tomcat is invoked as:
: $ ./apache-tomcat-5.5.20/bin/startup.sh
: It doesn't if Tomcat is invoked like this:
: $ cd ./apache-tomcat-5.5.20/bin
: $ startup.sh
that's not true. if you use JNDI or system properties to configure the
"solr home", then the working directory for Tomcat can be anything you
want. Solr only relies on the working directory as a fall back in the
absense of any other information about hwre it can find it's
configuration.
this is discussed at some length in the wikis on seting up solr for
Tomcat, cna you suggest any ways to make hte documentation more clear? ...
http://wiki.apache.org/solr/SolrInstall
http://wiki.apache.org/solr/SolrTomcat
: Another thing I don't understand is why Tomcat shows
: NoClassDefFoundError when the solr directory cannot
: be found in the current working directory. There is no
I suspect your were mislead by a situation in which multiple exceptions
were being logged. The SolrCore class will attempt to find it's
configuration, if it can not, it will throw an exception to that affect
which will be logged ... since it can't find it's configs the SolrCore
class will fail to load, which may then (aparently) cause Tomcat
to also log a NoClassDefFoundError. (I haven't tested this myself,
recently, i'm taking your word for it that's the error Tomcat produces)
The key to remember is that you have to "debug in order" start with teh
first error/warning/exception that is logged and look at it -- it may
frequently be the cause of other subsequent errors/warnings/exceptions.
-Hoss
