You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2018/02/21 06:58:00 UTC
[jira] [Comment Edited] (SOLR-7887) Upgrade Solr to use log4j2 --
log4j 1 now officially end of life
[ https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371018#comment-16371018 ]
Varun Thacker edited comment on SOLR-7887 at 2/21/18 6:57 AM:
--------------------------------------------------------------
More updates to the patch.
There is a bug which i'm looking into next :
When calling Log4j2Watcher#setLevelwhere category is "org.apache.solr.update.processor" the LoggerConfig returned is "root" so if we set it to DEBUG then the root logger changes and not just the individual class/package
{noformat}
LoggerConfig loggerConfig = getLoggerConfig(ctx, category);{noformat}
was (Author: varunthacker):
More updates to the patch.
There is a bug right now which i'm looking into next :
When calling Log4j2Watcher#setLevelwhere category is "org.apache.solr.update.processor" the LoggerConfig returned is "root" so if we set it to DEBUG then the root logger changes and not just the individual class/package
{noformat}
LoggerConfig loggerConfig = getLoggerConfig(ctx, category);{noformat}
> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
> Key: SOLR-7887
> URL: https://issues.apache.org/jira/browse/SOLR-7887
> Project: Solr
> Issue Type: Task
> Affects Versions: 5.2.1
> Reporter: Shawn Heisey
> Assignee: Varun Thacker
> Priority: Major
> Attachments: SOLR-7887-WIP.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final logging destination, so the admin UI has a log watcher that actually uses log4j and java.util.logging classes. That will need to be extended to add log4j2. I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j. Figuring out exactly which jars need to be in the lib/ext directory will take some research.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org