On 8/28/2013 2:59 PM, Tom Burton-West wrote:
Do you think I should open another JIRA and link it to yours or just add
this information (i.e. other scenarios where class loading not working) to
your JIRA?
The documentation does sound confused.
My personal opinion (which may not be what ends up happening) is that
${instanceDir}/lib shouldn't continue to be supported, at least not
implicitly without config, mostly because each instanceDir can be
dynamically destroyed (and added, with SolrCloud) by the core and
collection APIs.
I am guessing that you are seeing the same issue that has already been
documented. The little research I've done into this suggests that some
classes (ICUTokenizer being the specific example here) don't like it
when Solr replaces the classloader to add additional jars. This is
probably the case no matter which part of the config (solr.xml or
solrconfig.xml) tells Solr to replace the classloader.
The safest thing I've found is to use the lib directory off solr.home
(which gets automatically used) and don't specify any additional lib
directories anywhere in the configuration.
Thanks,
Shawn
