Josh Burchard created TIKA-3632:
-----------------------------------
Summary: Log4j appears to be running in a Servlet environment, but
there's no log4j-web module available
Key: TIKA-3632
URL: https://issues.apache.org/jira/browse/TIKA-3632
Project: Tika
Issue Type: Bug
Components: server
Affects Versions: 2.2.0
Environment: Windows 10
Reporter: Josh Burchard
I noticed the following issue when running the Tika server jar and trying to
troubleshoot log4j2 (with -Dlog4j2.debug set in the JVM):
{{INFO StatusLogger Log4j appears to be running in a Servlet environment, but
there's no log4j-web module available. If you want better web container
support, please add the log4j-web JAR to your web archive or server lib
directory.}}
Is this something that needs to be added when the server jar is built? It's
not _obviously_ impacting me right now but since it's a bit noisy (prints out
eight times) I attempted to quash the noise by downloading the
log4j-web-2.17.0.jar and add it to my classpath. Unfortunately that did nothing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
