[jira] [Commented] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available
[
https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463974#comment-17463974
]
Josh Burchard commented on TIKA-3632:
-
Thanks for the responses [~grossws] and [~tallison] and I appreciate the Wiki
update. I was working my way down to figuring out that I needed to enable
logging config for the child task, but the comment sped things up considerably.
But as you said, Tim, that's unrelated to the actual bug report since the
statement in question is still printed. It's still not causing me any direct
issue for me but I raised it just in case there is some performance impact.
Here's the source containing the error, if that's at all useful:
[https://logging.apache.org/log4j/2.0/log4j-core/apidocs/src-html/org/apache/logging/log4j/core/lookup/Interpolator.html]
And in the accepted answer for the below SO question there's some explanation
about what triggers the statement to print:
[https://stackoverflow.com/questions/37344431/why-log4j-thinks-my-project-run-in-servlet-environment/37345105]
> 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
>Assignee: Konstantin Gribov
>Priority: Minor
>
> 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)
[jira] [Commented] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available
[
https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463815#comment-17463815
]
Tim Allison commented on TIKA-3632:
---
Unrelated, but to just to make sure... tika-server 2.x runs by default in the
old --spawnChild mode. To set the jvm args in the forked process (which is the
process doing all the work) via tika-config.xml: \{{java -jar
tika-server-standard-2.2.1.jar -c tika-config.xml}}
{noformat}
-Xmx2g
-Dlog4j.configurationFile=my-forked-log4j2.xml
{noformat}
> 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
>Assignee: Konstantin Gribov
>Priority: Minor
>
> 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)
[jira] [Commented] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available
[
https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463513#comment-17463513
]
Konstantin Gribov commented on TIKA-3632:
-
I'll look into it. Seems it should be added from first glance
> 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
>Assignee: Konstantin Gribov
>Priority: Minor
>
> 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)
