You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2016/10/02 02:53:20 UTC
[jira] [Closed] (SOLR-2683) Solr classpath is not setup correctly
if core's instanceDir does not exist on startup
[ https://issues.apache.org/jira/browse/SOLR-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-2683.
---------------------------------------
Resolution: Won't Fix
instanceDir in solr.xml is long deprecated (gone?).
> Solr classpath is not setup correctly if core's instanceDir does not exist on startup
> -------------------------------------------------------------------------------------
>
> Key: SOLR-2683
> URL: https://issues.apache.org/jira/browse/SOLR-2683
> Project: Solr
> Issue Type: Bug
> Components: multicore
> Affects Versions: 4.0-ALPHA
> Reporter: Yury Kats
>
> When I launch Solr and the core's instanceDir does not exist, the directory is created, but none of the JARs listed in solrconfig.xml in <lib> entries are added to the classpath, thus resulting in ClassNotFound exceptions at runtime.
> <lib> entries in solrconfig.xml are relative to core's instanceDir. It seems that <lib> entries are processed before instanceDir is created and therefore can't be resolved.
> Example solr.xml:
> <cores adminPath="/admin/cores" defaultCoreName="master1">
> <core name="master1" instanceDir="master1" shard="shard1">
> </core>
> <core name="master2" instanceDir="master2" shard="shard2">
> </core>
> </cores>
> solrconfig.xml:
> ...
> <lib dir="../../dist" />
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org