[TIKA-4050] Forked child logs are overwritten upon restart

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.8.0
• Component/s: core

Environment

Windows 10 Enterprise

• Assignee: Unassigned
• Reporter: Josh Burchard
• Created: 23/May/23 19:31
• Updated: 14/Jul/23 13:55

Description

In my config file I specify a log file path for the forked child to use.  A problem arises when the child has a problem and the watchdog restarts it because the new child overwrites the previous child's log so I lose the details about what the child was doing prior to a restart.  Requesting that logging is preserved for all children while the watchdog is resident.

 

Reproduction steps:

dtikacfg.xml log4jTika.xml

1. ^{Launch tika server:
   java.exe -Djt="c:\tikatmp0000" -Dll="c:\tika0000.log" -Dcf="c:\log4jTika.xml" -jar "c:\tika-server-standard-2.8.0.jar" -c "c:\dtikacfg.xml"}
2. ^{Peek at the tika0000.log file and take note of the timestamps.}
3. ^{Kill the Tika child task and allow the watchdog to restart it.}
4. ^{Note that the previous content has been overwritten by log lines with new timestamps.}