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

Uwe Schindler commented on SOLR-3358:
-------------------------------------

Ryan: But you have now a classpath conflict. Depending on the order of jar 
files in filesystem and order of jar files resulting by that undefinedness, it 
can happen that log4j events are no longer transferred to slf4j (if user does 
*not* use log4j).

The log4j-over-slf is just a "catcher" for compatibility with external libs 
bundeled with Solr, that use log4j as their logging framework (it emulates 
log4j). The user has to sort out what chains he need to get correct logging, 
means: slf4 main jar, the delegator to log4j and log4j to do the actual work, 
or alternatively log4j-over-slf4j (to catch 3rd party logging events) and sl4fj 
(like it was before), that will log to JUL or nowhere. Theoretically maybe 
commons-logging cather is also needed for some 3rd party libs like 
commons-digester.

*I would like that we revert this commit and discuss the logging again!* This 
will be a pain for all WAR users and is already wrong because of duplicate 
class files in classpath leading to bugs or maybe even stack overflows because 
of logging-loops (I have seen that already, one logging framework delegates to 
another one and finally to itsself).
                
> Capture Logging Events from JUL and Log4j
> -----------------------------------------
>
>                 Key: SOLR-3358
>                 URL: https://issues.apache.org/jira/browse/SOLR-3358
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>         Attachments: SOLR-3358-compile-path.patch, SOLR-3358-logging.patch, 
> SOLR-3358-logging.patch
>
>
> The UI should be able to show the last few log messages.  To support this, we 
> will need to register an Appender (log4j) or Handler
> (JUL) and keep a buffer of recent log events.

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

Reply via email to