There is a recent JIRA issue about keeping the last n logs to display in the 
admin UI.

That introduced a problem - and then the fix introduced a problem - and then 
the fix mitigated the problem but left that ugly logging as a by product.

Don't remember the issue # offhand. I think there was a dispute about what 
should be done with it.

On May 1, 2012, at 11:14 AM, Benson Margulies wrote:

> CoreContainer.java, in the method 'load', finds itself calling
> loader.NewInstance with an 'fname' of Log4j of the slf4j backend is
> 'Log4j'.
> 
> e.g.:
> 
> 2012-05-01 10:40:32,367 org.apache.solr.core.CoreContainer  - Unable
> to load LogWatcher
> org.apache.solr.common.SolrException: Error loading class 'Log4j'
> 
> What is it actually looking for? Have I misplaced something?

- Mark Miller
lucidimagination.com











Reply via email to