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

Erick Erickson commented on SOLR-3022:
--------------------------------------

Hmmm, this didn't fix the problem for me in trunk. I defined a bogus 
requestHandler like this:
<requestHandler name="/eoe" class="eoe.solr.XmlUpdateRequestHandler"> 
</requestHandler>
and got the same annoying "No cores were created" error message with no clue 
why.

But if I put similar logic in RequestHandlers, around line 175 (the catch block 
in initHandlersFromConfig) I get useful traces. Or even just use 
SolrException.log rather than logOnce.

But this behavior is different than 3x and I'm wondering if anyone has a clue 
why things were changed and whether the change was intentional. I looked over 
some back copies of these files, and they haven't changed in a looong time with 
the one caveat that the error is getting re-thrown in 4x but just falls out in 
3x. 

So I'm looking for someone to weigh in on what the right thing to do is. I'm 
well aware that logging *everything* makes logging almost useless, but this 
behavior is suppressing useful information.

BTW, I ran into this same problem with a plugin I was fooling around with a 
while ago, I'm glad you're pursuing it, thanks. 
                
> AbstractPluginLoader does not log caught exceptions
> ---------------------------------------------------
>
>                 Key: SOLR-3022
>                 URL: https://issues.apache.org/jira/browse/SOLR-3022
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: James Dyer
>            Priority: Trivial
>             Fix For: 4.0
>
>         Attachments: SOLR-3022.patch
>
>
> I was setting up a new 4.x environment but forgot to put a custom Analyzer in 
> the classpath.  Unfortunately AbstractPluginLoader didn't log the exception 
> and it took a long time for me to figure out why "No cores were created".  

--
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