[
https://issues.apache.org/jira/browse/SOLR-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-3006.
------------------------------
Resolution: Duplicate
SOLR-2191 would probably fix this too
> Schema related problems are not logged
> --------------------------------------
>
> Key: SOLR-3006
> URL: https://issues.apache.org/jira/browse/SOLR-3006
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.0
> Environment: example run like: java -jar start.jar
> Reporter: Sami Siren
> Priority: Minor
> Attachments: SOLR-3006.patch
>
>
> If there's a problem in analyzer config or for example some mandatory
> attribute is missing from fieldType definition the resulting exception is not
> currently shown on log (console).
> The only thing visible, logged two times, is this:
> {code}
> SEVERE: Could not start Solr. Check solr/home property and the logs
> org.apache.solr.common.SolrException: No cores were created, please check the
> logs for errors
> {code}
> If I load the solr web page it shows the actual error(s). It would be nice if
> the problem was also logged on console/log.
> There's some suspicious looking lines in AbstractPluginLoader at around line
> 169:
> {code}
> SolrException e = new SolrException
> (ErrorCode.SERVER_ERROR,
> "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
> {code}
> where the SolrException is created with a constructor that sets the logged
> flag to true. Still there is a line
> {code}
> SolrException.logOnce(log,null,e);
> {code}
> a little later.
--
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: [email protected]
For additional commands, e-mail: [email protected]
