You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (Jira)" <ji...@apache.org> on 2022/12/07 17:52:00 UTC

[jira] [Commented] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j

    [ https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644453#comment-17644453 ] 

Sebastian Nagel commented on NUTCH-2978:
----------------------------------------

Hi Markus,

- the unit test of the plugin any23 fails
{noformat}
java.lang.NoSuchMethodError: 'void org.apache.logging.slf4j.Log4jLoggerFactory.<init>(org.apache.logging.slf4j.Log4jMarkerFactory)'
        at org.apache.logging.slf4j.SLF4JServiceProvider.initialize(SLF4JServiceProvider.java:54)
        at org.slf4j.LoggerFactory.bind(LoggerFactory.java:183)
        ...
        at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:414)
        at org.apache.hadoop.conf.Configuration.<clinit>(Configuration.java:229)
        at org.apache.nutch.util.NutchConfiguration.create(NutchConfiguration.java:64)
        at org.apache.nutch.any23.TestAny23IndexingFilter.testAny23TriplesFields(TestAny23IndexingFilter.java:39)
{noformat}
  There are already exclusions for slf4j in src/plugin/any23/ivy.xml, looks like this requires a closer look.

- Hadoop by now depends on reload4j (see HADOOP-18088): Did you already test whether this causes issues in distributed mode?

> Move to slf4j2 and remove log4j1 and reload4j
> ---------------------------------------------
>
>                 Key: NUTCH-2978
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2978
>             Project: Nutch
>          Issue Type: Task
>            Reporter: Markus Jelsma
>            Priority: Major
>         Attachments: NUTCH-2978.patch
>
>
> I got in trouble upgrading some dependencies and got a lot of LinkageErrors today, or with a Tika upgrade, disappearing logs. This patch fixes that by moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old log4j -> reload4j.
>  
> This patch fixes it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)