[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1743:
------------------------------
Attachment: SOLR-1743.patch
Here is a quick attempt at solving most of the rest of this.
The idea is:
reporting that the mutlicore core name is missing on the
http://localhost:8983/solr/admin/ page is now not always correct when SolrCore
is not put into the request.
Sometimes this means an error in one of the cores - though with the previous
part of this patch you only run into this issue when abortOnConfigError is
false.
But anyway, what this does is: if there is no default core specified, the old
error is shown - you are missing the corename.
If there is a default core specified (and there is by default these days -
collection1), and that core couldn't load, all of the errors found while
loading cores are printed to the page:
HTTP ERROR: 404
Severe errors in solr configuration.
Check your log files for more detailed information on what may be wrong.
The following are the errors registered by the cores you tried to load:
Could prob be a better message even.
Still, if you try and go to the full url of a core that couldn't load, you
will get page not found - because the core will have never loaded. Would be
nice to see the error there too, but this is as far as I go at the moment.
This patch also removes a System.out in the last patch and fixes a bug in
reading the defaultCoreName from solr.xml - it was looking for it at /solr when
it should have been looking at /solr/cores.
> error reporting is rendering "404 missing core name in path" for all type of
> errors
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1743
> URL: https://issues.apache.org/jira/browse/SOLR-1743
> Project: Solr
> Issue Type: Bug
> Components: Build
> Environment: all
> Reporter: Marcin
> Assignee: Mark Miller
> Fix For: 1.5
>
> Attachments: SOLR-1743.patch, SOLR-1743.patch, SOLR-1743.patch
>
>
> despite the error in schema syntax or any other type of error you will always
> get:
> "404 missing core name in path" communicate.
> cheers,
> /Marcin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
