[
https://issues.apache.org/jira/browse/TIKA-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353505#comment-17353505
]
Tim Allison commented on TIKA-3424:
-----------------------------------
{noformat}
DEBUG StatusLogger Reconfiguration complete for context[name=70dea4e] at URI
jar:file:/yadayada/tika-app-2.0.0-SNAPSHOT.jar!/log4j2.properties
(org.apache.logging.log4j.core.LoggerContext@5d76b067) with optional
ClassLoader: null
DEBUG StatusLogger Shutdown hook enabled. Registering a new one.
DEBUG StatusLogger LoggerContext[name=70dea4e,
org.apache.logging.log4j.core.LoggerContext@5d76b067] started OK.
DEBUG StatusLogger Stopping LoggerContext[name=70dea4e,
org.apache.logging.log4j.core.LoggerContext@5d76b067]
DEBUG StatusLogger Stopping LoggerContext[name=70dea4e,
org.apache.logging.log4j.core.LoggerContext@5d76b067]...
TRACE StatusLogger Unregistering 1 MBeans:
[org.apache.logging.log4j2:type=70dea4e]
TRACE StatusLogger Unregistering 1 MBeans:
[org.apache.logging.log4j2:type=70dea4e,component=StatusLogger]
TRACE StatusLogger Unregistering 1 MBeans:
[org.apache.logging.log4j2:type=70dea4e,component=ContextSelector]
TRACE StatusLogger Unregistering 1 MBeans:
[org.apache.logging.log4j2:type=70dea4e,component=Loggers,name=]
TRACE StatusLogger Unregistering 1 MBeans:
[org.apache.logging.log4j2:type=70dea4e,component=Appenders,name=STDERR]
TRACE StatusLogger Unregistering but no MBeans found matching
'org.apache.logging.log4j2:type=70dea4e,component=AsyncAppenders,name=*'
TRACE StatusLogger Unregistering but no MBeans found matching
'org.apache.logging.log4j2:type=70dea4e,component=AsyncLoggerRingBuffer'
TRACE StatusLogger Unregistering but no MBeans found matching
'org.apache.logging.log4j2:type=70dea4e,component=Loggers,name=*,subtype=RingBuffer'
TRACE StatusLogger Stopping
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@1d8d30f7...
TRACE StatusLogger PropertiesConfiguration notified 2 ReliabilityStrategies
that config will be stopped.
TRACE StatusLogger PropertiesConfiguration stopping 1 LoggerConfigs.
TRACE StatusLogger PropertiesConfiguration stopping root LoggerConfig.
TRACE StatusLogger PropertiesConfiguration notifying ReliabilityStrategies that
appenders will be stopped.
TRACE StatusLogger PropertiesConfiguration stopping remaining Appenders.
DEBUG StatusLogger Shutting down OutputStreamManager SYSTEM_OUT.false.false
DEBUG StatusLogger OutputStream closed
DEBUG StatusLogger Shut down OutputStreamManager SYSTEM_OUT.false.false, all
resources released: true
DEBUG StatusLogger Appender STDERR stopped with status true
TRACE StatusLogger PropertiesConfiguration stopped 1 remaining Appenders.
TRACE StatusLogger PropertiesConfiguration cleaning Appenders from 2
LoggerConfigs.
DEBUG StatusLogger Stopped
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@1d8d30f7
OK
DEBUG StatusLogger Stopped LoggerContext[name=70dea4e,
org.apache.logging.log4j.core.LoggerContext@5d76b067] with status true
{noformat}
The correct config file is being loaded and looks to be configured for stderr,
and yet, I can confirm that logs coming from tika-core, which uses slf4j, are
going to stdout.
> tika-app in 2.x should log to stderr
> ------------------------------------
>
> Key: TIKA-3424
> URL: https://issues.apache.org/jira/browse/TIKA-3424
> Project: Tika
> Issue Type: New Feature
> Reporter: Tim Allison
> Priority: Major
>
> Tika 2.x's app is logging to stdout. We tried to write to stderr via the
> log4j2.properties file, but that is not being respected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
