lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Laban (JIRA)" <>
Subject [jira] [Commented] (SOLR-7887) Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
Date Wed, 01 Jun 2016 21:38:59 GMT


Keith Laban commented on SOLR-7887:

If you notice the first note here
 bq. They must not access methods and classes internal to the Log4j 1.x implementation such
as Appenders, LoggerRepository or Category's callAppenders method.

Unfortunately, hdfs extends {{AppenderSkeleton}} which violates this rule causing the bridge
solution not to work.

As far as I can tell there are only two soltuions:

# continue to bring in bring in log4j 1.2 -- I think all of the packages have changed in the
upgrade so that should hopefully work
# hdfs/hadoop needs to upgrade to log4j2 

Not sure what other options there are

> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>                 Key: SOLR-7887
>                 URL:
>             Project: Solr
>          Issue Type: Task
>    Affects Versions: 5.2.1
>            Reporter: Shawn Heisey
>         Attachments: SOLR-7887-WIP.patch
> The logging services project has officially announced the EOL of log4j 1:
> 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

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

View raw message