Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
None
-
None
-
None
Description
In a private message kkrugler pointed out that log4j2 was not being correctly configured in tika-app when running in batch mode:
INFO [Thread-1] 13:23:32,119 org.apache.tika.batch.BatchProcessDriverCLI BatchProcess: ERROR StatusLogger Reconfiguration failed: No configuration found for '4b85612c' at 'null' in 'null'
Separately, I noticed that --config=some-tika-config.xml was breaking the commandline when running tika-app in batch mode.