shawn, as you discovered, the double logging problem is because additivity is default enabled and you have solr event defined specifically AND in the root logger
-- on your log4jv2 v logback investigation logback IS "log4j done right" and the way to go. its here today and works. http://logback.qos.ch/reasonsToSwitch.html I've never understood the point of the log4j2 project. or why folks still want to use log4j given its deficiencies relative to logback. ;) -- is this a good place to ask about a few logging related items re: solr support for them? -more up to date slf4j included in the distribution (e.g 1.7.7) . slf4j has gotten more than a few updates in the 8 release since 1.6.6 (which is what is currently packaged with solr) http://www.slf4j.org/news.html -if not switching to logback, a more up to date log4j included in the distribution (e.g. 1.2.17) (since that seems to be the logger of choice for the solr devs) -if sticking with log4j, switching to the log4j.xml version of the config file which allows some more configuration options and is apparently the current preferred format -if sticking with log4j, consider also packaging the log4j extras jar to extend the capabilities of regular log4j and get it closer to logback (e.g. log rotation with compression) https://logging.apache.org/log4j/extras/changes-report.html https://logging.apache.org/log4j/extras/apidocs/index.html -fixing the solr logging UI display so it can work even if the solr events are NOT sent to the root logger. (maybe this UI interface should allow picking a specific log file defined in the logging configuration for max flexibility?) its easy enough to make all these changes after the fact and with the exception of the solr logger UI not working, there is very little technical effort required ________________________________________ From: Shawn Heisey <s...@elyograg.org> Sent: Sunday, April 13, 2014 08:22 To: solr-user@lucene.apache.org Subject: Re: stucked with log4j configuration On 4/12/2014 9:33 PM, Bill Bell wrote: > Well I hope log4j2 is something Solr supports when GA The biggest holdup would be the fact that slf4j doesn't yet have a binding for log4j2. A new log watcher (for the admin UI) is probably required too. The logback project page looks almost identical to the slf4j project page. Logback is a native logging implementation in slf4j. I'm guessing the two projects have the same author and/or the same dev team. The "between the lines" message I get from the Logback project page is that it is "log4j done right." http://slf4j.org/ http://logback.qos.ch/ Because they have a product that competes with log4j2 in more than just function, they probably won't add log4j2 support before GA. Hopefully they WILL add it. Thanks, Shawn
