[
https://issues.apache.org/jira/browse/TIKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381501#comment-17381501
]
Hudson commented on TIKA-3480:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #282 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/282/])
TIKA-3480 -- add pipesClientId as property to the classpath in the forked
process (tallison:
[https://github.com/apache/tika/commit/1bf79652e3c2094a9e8532bb5e6694d07803b2b8])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
* (add) tika-core/src/test/resources/log4j2.xml
* (delete) tika-core/src/test/resources/log4j.properties
> Add pipesClientId to pipes forked process for better logging
> -------------------------------------------------------------
>
> Key: TIKA-3480
> URL: https://issues.apache.org/jira/browse/TIKA-3480
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.1
>
>
> Given that pipes forks processes, it would be convenient to configure log4j2
> to output one log file per forked process given that log4j2 can't handle
> multiple processes writing to the same file.
> A file appender in the log4j2-async.xml file might look something like this:
> {noformat}
> <Appenders>
> <File name="file-appender"
> fileName="logs/client-${sys:pipesClientId}.log">
> <PatternLayout pattern="%-5p [%t] %d{HH:mm:ss,SSS} %c %m%n"/>
> </File>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
