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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Thanks for picking it up. I am very happy this one is resolved now. Thanks 
Sebastian for testing!

> 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
> Fix For: 1.20
>
> Attachments: NUTCH-2978-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Hudson (Jira)]

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

Hudson commented on NUTCH-2978:
---

SUCCESS: Integrated in Jenkins build Nutch » Nutch-trunk #112 (See 
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/112/])
NUTCH-2978, upgrade to slf4j2 throughout, first steps (tallison: 
[https://github.com/apache/nutch/commit/cf74770f9642356d4c2cdc9d6f41aaf8a8928bcf])
* (edit) src/plugin/lib-rabbitmq/ivy.xml
* (edit) src/plugin/any23/ivy.xml
* (edit) src/plugin/any23/plugin.xml
* (edit) src/plugin/build-plugin.xml
* (edit) ivy/ivy.xml
NUTCH-2978 -- exclude reload4j and update LICENSE-binary and NOTICE-binary. 
(tallison: 
[https://github.com/apache/nutch/commit/daedbc36ceeba506795973b75ead2f5b4b59ddd9])
* (edit) ivy/ivy.xml
* (edit) LICENSE-binary
* (edit) NOTICE-binary
NUTCH-2978 -- update slf4j-api (tallison: 
[https://github.com/apache/nutch/commit/51055ef47ac09e082ae74bfa2720a84af431da19])
* (edit) ivy/ivy.xml


> 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
> Fix For: 1.20
>
> Attachments: NUTCH-2978-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison merged PR #772:
URL: https://github.com/apache/nutch/pull/772




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1722508915

   Fantastic! Thank you so much Sebastian!
   
   On Sun, Sep 17, 2023 at 9:02 AM Sebastian Nagel ***@***.***>
   wrote:
   
   > +1
   >
   > A test with the pseudo-distributed Hadoop setup
   >  was
   > successful:
   >
   >- Nutch tools work properly, no issues
   >- as expected, Hadoop puts slf4j-api-1.7.36.jar and
   >slf4j-reload4j-1.7.36.jar in the classpath in front of the Nutch job 
jars
   >- consequently, task logs are formatted using the format defined in
   >$HADOOP_HOMe/etc/hadoop/log4j.properties
   >- (the good thing) log messages from Nutch classes appear in the task
   >logs, e.g.
   >
   > 2023-09-17 07:29:21,726 INFO [FetcherThread] 
org.apache.nutch.fetcher.FetcherThread: FetcherThread 33 fetching 
https://nutch.apache.org/ (queue crawl delay=5000ms)
   >
   >- the log format defined in $NUTCH_HOME/conf/log4j2.xml is only
   >applied to the logs of the Yarn job client, e.g.
   >
   >2023-09-17 07:29:32,432 INFO fetcher.Fetcher: Fetcher: finished at 
2023-09-17 07:29:32, elapsed: 00:00:25
   >
   >- in addition, I've included two PDFs, a XLSX and a ePub document, to
   >test the Tika parser: the docs were successfully parsed using Tika 
2.3.0 -
   >if necessary I can repeat the test for NUTCH-2959
   >
   >
   > —
   > Reply to this email directly, view it on GitHub
   > , or
   > unsubscribe
   > 

   > .
   > You are receiving this because you authored the thread.Message ID:
   > ***@***.***>
   >
   




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

sebastian-nagel commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1722472438

   +1
   
   A test with the [pseudo-distributed Hadoop 
setup](https://github.com/sebastian-nagel/nutch-test-single-node-cluster/) was 
successful:
   - Nutch tools work properly, no issues
   - as expected, Hadoop puts slf4j-api-1.7.36.jar and 
slf4j-reload4j-1.7.36.jar in the classpath in front of the Nutch job jars
   - consequently, task logs are formatted using the format defined in 
`$HADOOP_HOMe/etc/hadoop/log4j.properties`
   - (the good thing) log messages from Nutch classes appear in the task logs, 
e.g.
 ```
  2023-09-17 07:29:21,726 INFO [FetcherThread] 
org.apache.nutch.fetcher.FetcherThread: FetcherThread 33 fetching 
https://nutch.apache.org/ (queue crawl delay=5000ms)
 ```
   - the log format defined in `$NUTCH_HOME/conf/log4j2.xml` is only applied to 
the logs of the Yarn job client, e.g.
 ```
 2023-09-17 07:29:32,432 INFO fetcher.Fetcher: Fetcher: finished at 
2023-09-17 07:29:32, elapsed: 00:00:25
 ```
   - in addition, I've included two PDFs, a XLSX and a ePub document, to test 
the Tika parser: the docs were successfully parsed using Tika 2.3.0 - if 
necessary I can repeat the test for NUTCH-2959
   




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1720326084

   Y, of course. That'd be fantastic. Thank you!




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

sebastian-nagel commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1719977976

   > I'll merge this in a day or so unless anyone has objections.
   
   Give me a few more days, over the weekend. I'd like to test it at least on a 
[pseudo-distributed Hadoop 
setup](https://github.com/sebastian-nagel/nutch-test-single-node-cluster/). If 
this is successful, then a failure on a fully distributed Hadoop cluster is 
rather unlikely.




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1719961162

   I'll merge this in a day or so unless anyone has objections.




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison commented on PR #772:
URL: https://github.com/apache/nutch/pull/772#issuecomment-1717765669

   If folks could test this out on their workloads, that'd be fantastic!  It 
works on mine, but I'm really hesitant to merge until someone else runs it.  
Thank you!




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Tim Allison (Jira)]

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

Tim Allison commented on NUTCH-2978:


I haven't tested in hadoop. I've just run it locally, and, for the modules I'm 
using, it seems to work.

Please, please, please help test it more broadly!

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

You managed to get it up and running, as well when deployed on Hadoop? This 
ticket almost drove me to tears and despair :D

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Tim Allison (Jira)]

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

Tim Allison commented on NUTCH-2978:


K, I think https://github.com/apache/nutch/pull/772 is better.  This is nearly 
entirely based on [~markus17]'s patches.  Let me know what you think.

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison opened a new pull request, #772:
URL: https://github.com/apache/nutch/pull/772

   Thanks for your contribution to [Apache Nutch](https://nutch.apache.org/)! 
Your help is appreciated!
   
   Before opening the pull request, please verify that
   * there is an open issue on the [Nutch issue 
tracker](https://issues.apache.org/jira/projects/NUTCH) which describes the 
problem or the improvement. We cannot accept pull requests without an issue 
because the change wouldn't be listed in the release notes.
   * the issue ID (`NUTCH-2978`)
 - is referenced in the title of the pull request
 - and placed in front of your commit messages surrounded by square 
brackets (`[NUTCH-] Issue or pull request title`)
   * commits are squashed into a single one (or few commits for larger changes)
   * Java source code follows [Nutch Eclipse Code Formatting 
rules](https://github.com/apache/nutch/blob/master/eclipse-codeformat.xml)
   * Nutch is successfully built and unit tests pass by running `ant clean 
runtime test`
   * there should be no conflicts when merging the pull request branch into the 
*recent* master branch. If there are conflicts, please try to rebase the pull 
request branch on top of a freshly pulled master branch.
   * if new dependencies are added,
 - are these dependencies licensed in a way that is compatible for 
inclusion under [ASF 
2.0](https://www.apache.org/legal/resolved.html#category-a)?
 - are `LICENSE-binary` and `NOTICE-binary` updated accordingly?
   
   We will be able to faster integrate your pull request if these conditions 
are met. If you have any questions how to fix your problem or about using Nutch 
in general, please sign up for the [Nutch mailing 
list](https://nutch.apache.org/mailing_lists.html). Thanks!
   




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison closed pull request #769: NUTCH-2978 

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison commented on PR #769:
URL: https://github.com/apache/nutch/pull/769#issuecomment-1696087426

   This is a draft.  More work is required.  Please help. :D




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[ASF GitHub Bot (Jira)]

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

ASF GitHub Bot commented on NUTCH-2978:
---

tballison opened a new pull request, #769:
URL: https://github.com/apache/nutch/pull/769

   Thanks for your contribution to [Apache Nutch](https://nutch.apache.org/)! 
Your help is appreciated!
   
   Before opening the pull request, please verify that
   * there is an open issue on the [Nutch issue 
tracker](https://issues.apache.org/jira/projects/NUTCH) which describes the 
problem or the improvement. We cannot accept pull requests without an issue 
because the change wouldn't be listed in the release notes.
   * the issue ID (`NUTCH-`)
 - is referenced in the title of the pull request
 - and placed in front of your commit messages surrounded by square 
brackets (`[NUTCH-] Issue or pull request title`)
   * commits are squashed into a single one (or few commits for larger changes)
   * Java source code follows [Nutch Eclipse Code Formatting 
rules](https://github.com/apache/nutch/blob/master/eclipse-codeformat.xml)
   * Nutch is successfully built and unit tests pass by running `ant clean 
runtime test`
   * there should be no conflicts when merging the pull request branch into the 
*recent* master branch. If there are conflicts, please try to rebase the pull 
request branch on top of a freshly pulled master branch.
   * if new dependencies are added,
 - are these dependencies licensed in a way that is compatible for 
inclusion under [ASF 
2.0](https://www.apache.org/legal/resolved.html#category-a)?
 - are `LICENSE-binary` and `NOTICE-binary` updated accordingly?
   
   We will be able to faster integrate your pull request if these conditions 
are met. If you have any questions how to fix your problem or about using Nutch 
in general, please sign up for the [Nutch mailing 
list](https://nutch.apache.org/mailing_lists.html). Thanks!
   




> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Ah nope, this is not it. Parse-tika throws lots of errors and stack traces, 
although it does work. We now get:

{color:#00}java.util.ServiceConfigurationError: 
org.apache.logging.log4j.spi.Provider: 
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype{color}

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

New patch now makes sure there is a log4j 2.19 in tika and mentioned in its 
plugin.xml, otherwise above will happen. Now i am not sure the other plugins 
are still ok.

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Ok, i also wanted to get rid of loose log4j libs. There was still one in any23 
and parse-tika. When removing the lib from parse-tika, lots of bad things 
happen.
{code:java}
22/12/16 13:36:03 WARN ooxml.OPCPackageDetector: Unable to load 
org.apache.tika.detect.microsoft.ooxml.OPCPackageDetector
java.lang.NoClassDefFoundError: org/apache/logging/log4j/LogManager
        at org.apache.poi.ooxml.POIXMLRelation.(POIXMLRelation.java:54)
        at 
org.apache.tika.detect.microsoft.ooxml.OPCPackageDetector.(OPCPackageDetector.java:106)
        at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
        at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at java.base/java.lang.Class.newInstance(Class.java:584)
        at 
org.apache.tika.utils.ServiceLoaderUtils.newInstance(ServiceLoaderUtils.java:80)
        at 
org.apache.tika.config.ServiceLoader.loadStaticServiceProviders(ServiceLoader.java:345)
        at 
org.apache.tika.config.ServiceLoader.loadStaticServiceProviders(ServiceLoader.java:312)
        at 
org.apache.tika.detect.zip.DefaultZipContainerDetector.(DefaultZipContainerDetector.java:85)
        at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
        at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at 
org.apache.tika.utils.ServiceLoaderUtils.newInstance(ServiceLoaderUtils.java:78)
        at 
org.apache.tika.config.ServiceLoader.loadStaticServiceProviders(ServiceLoader.java:345)
        at 
org.apache.tika.detect.DefaultDetector.getDefaultDetectors(DefaultDetector.java:90)
        at 
org.apache.tika.detect.DefaultDetector.(DefaultDetector.java:50)
        at 
org.apache.tika.detect.DefaultDetector.(DefaultDetector.java:55)
        at 
org.apache.tika.config.TikaConfig.getDefaultDetector(TikaConfig.java:264)
        at 
org.apache.tika.config.TikaConfig$DetectorXmlLoader.createDefault(TikaConfig.java:1017)
        at 
org.apache.tika.config.TikaConfig$DetectorXmlLoader.createDefault(TikaConfig.java:975)
        at 
org.apache.tika.config.TikaConfig$XmlLoader.loadOverall(TikaConfig.java:630)
        at org.apache.tika.config.TikaConfig.(TikaConfig.java:155)
        at org.apache.tika.config.TikaConfig.(TikaConfig.java:145)
        at org.apache.tika.config.TikaConfig.(TikaConfig.java:120)
        at org.apache.nutch.parse.tika.TikaParser.setConf(TikaParser.java:276)
        at 
org.apache.nutch.plugin.Extension.getExtensionInstance(Extension.java:177)
        at 
org.apache.nutch.parse.ParserFactory.getParsers(ParserFactory.java:136)
        at org.apache.nutch.parse.ParseUtil.parse(ParseUtil.java:75)
        at 
org.apache.nutch.indexer.IndexingFiltersChecker.process(IndexingFiltersChecker.java:245)
        at 
org.apache.nutch.util.AbstractChecker.processSingle(AbstractChecker.java:87)
        at 
org.apache.nutch.indexer.IndexingFiltersChecker.run(IndexingFiltersChecker.java:136)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:81)
        at 
org.apache.nutch.indexer.IndexingFiltersChecker.main(IndexingFiltersChecker.java:316)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.apache.hadoop.util.RunJar.run(RunJar.java:323)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:236)
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.LogManager
        at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
        at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
        at 
org.apache.nutch.plugin.PluginClassLoader.loadClassFromSystem(PluginClassLoader.java:105)
        at 
org.apache.nutch.plugin.PluginClassLoader.loadClassFromParent(PluginClassLoader

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Patch now includes Sebastian's patch, and actually contains the upgrade from 
old slf4j to the new 2.0.6. Tested on Hadoop 3.3.4 cluster with a parsing 
fetcher. This went just fine.

-I must admist that those slf4js and jcl-over-slf remaining in the plugins do 
bother me to some degree.-

New patch now includes exclusions to get rid of all of them.

> 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-1.patch, NUTCH-2978-2.patch, 
> NUTCH-2978-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Ah yes, thanks! I am not sure if a 'solution' will come from Tika, that 
specific package seems to be shaded in all versions between 2.3.0 and 2.6.0. 
But, we, ASF Nutch, do not depend on it so we are good.

Patched like this, Nutch will fetch/parse just fine when running on Hadoop. I 
did get this when doing an indexchecker using the job file:

{color:#00}ERROR StatusLogger Log4j2 could not find a logging 
implementation. Please add log4j-core to the classpath. Using SimpleLogger to 
log to the console...{color}


 

{color:#00}However, logging worked just fine.{color}

 

> 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-any23.patch, 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)

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

[Sebastian Nagel (Jira)]

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

Sebastian Nagel commented on NUTCH-2978:


{quote}there was a slf4j jar packaged within the tika-parser-scientific 
package{quote}
See the exclusions in src/plugin/parse-tika/ivy.xml

{quote}xerces/xml-apis{quote}
Excluded as well from parse-tika. Many of the classes in xml-apis are for Java 
11 also covered by the [module 
java.xml|https://docs.oracle.com/en/java/javase/11/docs/api/java.xml/module-summary.html].

{quote}Something to look out for when upgrading Tika.{quote}

[~markus17], do you want to wait and verify whether a solution of this issue 
allows to upgrade Tika? Or are the patch(es) ready to commit?

> 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-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

About the slf issues,

Somewhere another slf4j jar was lurking in the job file, but i couldn't find it 
for a long while. Until i saw there was a slf4j jar packaged within the 
tika-parser-scientific-package! I got rid of it, then got a xerces/xml-apis 
error, which i then also excluded. Now there are many other errors.

Something to look out for when upgrading Tika. But for some reason, although we 
are using the same Tika version, that specific package does not appear as a 
dependency of Tika in in Nutch' vanilla. That may change later.

> 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-any23.patch, 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)

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

[Sebastian Nagel (Jira)]

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

Sebastian Nagel commented on NUTCH-2978:


Attached additional patch for the any23 plugin. Unit tests now pass.

The patch also adds the ant dependencytree targets to the plugins' build.xml - 
good to have in order to figure out the reason for the NoSuchMethod error.

> 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-any23.patch, 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Ah, well. I also tried a Tika parsing fetcher of a vanilla 1.20 Nutch with just 
this patch, and the generator patch. It works!

Not sure why our parser stuff fails, but at least Nutch' stuff is working!

> 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

This morning i saw one of our internal projects spewing the same error as 
any23, it was quickly remedied by upgrading a dependency further down the line. 
Not sure if this will go as easy with the any23 plugin, i'll take a look

Regarding running on Hadoop, I just ran a patched 1.20 CrawldbReader job on a 
3.3.4 cluster, i ran flawless! Encouranged by the result i quickly ran a 
generate, followed by a fetch. The fetch failed due to LinkageError in our 
parser plugin, similar as parse-tika. Too bad.

A local indexchecker runs fine, an indexchecker using a job file fails with the 
same error.

 

 

 

 

> 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)

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

[Markus Jelsma (Jira)]

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

Markus Jelsma commented on NUTCH-2978:
--

Yes, i saw the slf4j present in the plugin, it troubled my already when i 
attempted an upgrade to a newer Tika version.

Regarding reload4j, i was already worried it might not run in distributed mode 
but haven't tested it yet. For now i am glad enough Nutch runs our Tika based 
parser in local mode.

To be continued

> 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)

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

[Sebastian Nagel (Jira)]

[ 
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.(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.(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)