[ 
https://issues.apache.org/jira/browse/SOLR-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591071#comment-13591071
 ] 

Hoss Man commented on SOLR-4373:
--------------------------------

bq. I'm still experiencing the same problems (rev 1450937): Libraries cannot be 
found. 
...
bq. The first time I create a core it fails, however the second time it 
succeeds.

On the same instance? or do you mean you get an error creating shard1 on port 
8080, but when you create shard2 on 8081 that works?

That sounds like it is a probably a distinct, semi-related, bug.

can you please file a new jira, and include: both the svn rev _and_ branch you 
are using (trunk vs 4x), the details of the configs you are using, the details 
of the errors you get (full logs would be nice so we can see the core startup 
info), and when/where you get those errors in the process of your script (ie: 
is it when creating the collection? linking the config to the collection? 
creating the cores?)
                
> 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
>            Reporter: Alexandre Rafalovitch
>            Priority: Blocker
>              Labels: lib, multicore
>             Fix For: 4.2, 5.0, 4.1.1
>
>         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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to