[
https://issues.apache.org/jira/browse/SOLR-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600623#comment-13600623
]
Alexandre Rafalovitch commented on SOLR-4373:
---------------------------------------------
I confirm that this is fixed in 4.2 with my original test case setup.
> In multicore, lib directives in solrconfig.xml cause conflict and clobber
> directives from earlier cores
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4373
> URL: https://issues.apache.org/jira/browse/SOLR-4373
> Project: Solr
> Issue Type: Bug
> Components: multicore
> Affects Versions: 4.1, 4.2
> Reporter: Alexandre Rafalovitch
> Assignee: Hoss Man
> Labels: lib, multicore
> Fix For: 4.2
>
> Attachments: multicore-bug.zip, testscript.sh
>
>
> Having lib directives in the solrconfig.xml files of multiple cores can cause
> problems when using multi-threaded core initialization -- which is the
> default starting with Solr 4.1.
> The problem manifests itself as init errors in the logs related to not being
> able to find classes located in plugin jars, even though earlier log messages
> indicated that those jars had been added to the classpath.
> One work around is to set {{coreLoadThreads="1"}} in your solr.xml file --
> forcing single threaded core initialization. For example...
> {code}
> <?xml version="1.0" encoding="utf-8" ?>
> <solr coreLoadThreads="1">
> <cores adminPath="/admin/cores">
> <core name="core1" instanceDir="core1" />
> <core name="core2" instanceDir="core2" />
> </cores>
> </solr>
> {code}
> (Similar problems may occur if multiple cores are initialized concurrently
> using the /admin/cores handler)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
