[ 
https://issues.apache.org/jira/browse/SOLR-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomás Fernández Löbbe updated SOLR-3477:
----------------------------------------

    Attachment: SOLR-3477-3_6.patch
                SOLR-3477.patch

I checked this and saw the same as Tommaso, it seems to work on trunk and 4x 
branch. 
I added a test case that start the CoreContainer with no cores (a solr.xml file 
with an empty list of cores). It works on trunk and fails on 3.6 with an 
exception as the one described in the description of this issue.
                
> SOLR does not start up when no cores are defined
> ------------------------------------------------
>
>                 Key: SOLR-3477
>                 URL: https://issues.apache.org/jira/browse/SOLR-3477
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.6
>         Environment: All environments
>            Reporter: Sebastian Schaffert
>            Priority: Critical
>         Attachments: SOLR-3477-3_6.patch, SOLR-3477.patch
>
>
> Since version 3.6.0, Solr does not start up when no cores are defined in 
> solr.xml. The problematic code is in CoresContainer.java, lines 171-173.
> org.apache.solr.common.SolrException: No cores were created, please check the 
> logs for errors
>       at 
> org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:172)
>  ~[solr-core-3.6.0.jar:3.6.0 1310449 - rmuir - 2012-04-06 11:34:38]
>       at 
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:96) 
> ~[solr-core-3.6.0.jar:3.6.0 1310449 - rmuir - 2012-04-06 11:34:38]
> ...
> In our case, this is however a valid situation, because we create the cores 
> programatically by calling the webservices to register new cores. The server 
> is initially started with no cores defined, and depending on the 
> configuration of our application, cores are then created dynamically.
> For the time being, we have to stick with version 3.5, which did not have 
> this problem (or feature).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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