lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Commented] (SOLR-4129) Solr doesn't support log4j
Date Fri, 30 Nov 2012 17:46:00 GMT


Shawn Heisey commented on SOLR-4129:

I've been trying to work out what is being said here and I'm finding it hard to follow.  I'm
especially confused by the part about log4j-over-slf4j.

If this means that I will be able to change logging levels for log4j within the GUI, I'm all
for it.  I'm less concerned about being able to view the log within the GUI, but that would
be a nice addition.

I use log4j with Solr, and I've included log4j-over-slf4j.  To make it a lot easier to build
that way, I patched solr/build.xml, that patch is attached to SOLR-3918.  I have the following
jars in jetty's lib/ext:


> Solr doesn't support log4j 
> ---------------------------
>                 Key: SOLR-4129
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
>            Reporter: Raintung Li
>              Labels: log
>             Fix For: 4.1, 5.0
>         Attachments: patch-4129.txt
> For many project use the log4j, actually solr use slf logger framework, slf can easy
to integrate with log4j by design. 
> Solr use log4j-over-slf.jar to handle log4j case.
> This jar has some issues.
> a. Actually last invoke slf to print the logger (For solr it is JDK14.logging).
> b. Not implement all log4j function. ex. Logger.setLevel() 
> c. JDK14 log miss some function, ex., day rolling 
> Some dependence project had been used log4j that the customer still want to use it. JDK14
log has many different with Log4j, at least configuration file can't reuse.
> The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project
have to remove log4j.
> I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message