[
https://issues.apache.org/jira/browse/SOLR-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265880#comment-13265880
]
Ryan McKinley commented on SOLR-3426:
-------------------------------------
right -- if you are using Log4j, the LogWatcher stuff will not work.
In the current behavior, you should get a warning in the logs and when you try
the logging UI it will give a warning that it did not load.
See: SOLR-3399 and SOLR-3358 that look at ways to capture log4j events.
> CoreContainer goes looking for nonexistent Log4j class
> ------------------------------------------------------
>
> Key: SOLR-3426
> URL: https://issues.apache.org/jira/browse/SOLR-3426
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Benson Margulies
>
> The code quoted here from CoreContainer.java ends up looking for a class
> named Log4j instead of Log4jWatcher. Neither name exists in the tree.
> // Now load the framework
> if(fname!=null) {
> if("JUL".equalsIgnoreCase(fname)) {
> logging = new JulWatcher(slf4jImpl);
> }
> // else if( "Log4j".equals(fname) ) {
> // logging = new Log4jWatcher(slf4jImpl);
> // }
> else {
> try {
> logging = loader.newInstance(fname, LogWatcher.class);
> }
> catch (Throwable e) {
> log.warn("Unable to load LogWatcher", e);
> }
> }
--
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]
