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 18:09:59 GMT


Shawn Heisey commented on SOLR-4129:

bq. Shawn, how could you have both log4j-over-slf4 and log4j itself on the classpath? That
doesn't make sense and SLF4J will probably complain; if it doesn't it's still an error. If
your intent is to use Log4j then remove log4j-over-slf4.

I did this because I didn't know any better.  I'm a bit of a beginner in the Java universe.
 I added the slf4j things included in the standard WAR except for the JUL binding, then added
the log4j binding and log4j.  There are no complaints about it in my log.  It's probably not
complaining because alphabetically, the real log4j jar comes before the slf4j one, so when
the import is done, the right class gets loaded.

After removing log4j-over-slf4j, Solr still seems fine.  Both before and after the removal,
logging at WARN, the only log entry I get is "Log watching is not yet implemented for log4j."

I would like to have short logs saying that each core has been started and that Solr is fully
started.  Would it be reasonable to file a jira asking for this to happen at WARN, or would
I just have to figure out which class(es) to set to INFO in my log4j config?

> 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