lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Updated] (SOLR-3477) SOLR does not start up when no cores are defined
Date Fri, 01 Jun 2012 21:43:23 GMT


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

    Attachment: SOLR-3477-3_6.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:
>             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, lines 171-173.
> org.apache.solr.common.SolrException: No cores were created, please check the logs for
> 	at org.apache.solr.core.CoreContainer$Initializer.initialize(
~[solr-core-3.6.0.jar:3.6.0 1310449 - rmuir - 2012-04-06 11:34:38]
> 	at org.apache.solr.servlet.SolrDispatchFilter.init( ~[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
> 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message