Test case:

Create a harvester.
Execute it and check the harvester history tab. The execution has a button to download the log file.
Execute it 2 or more times and check the harvester history tab. Most probably is that the latest executions don't have the button to download the log file. Checking the previous log files, you can find out that are stored there.

The problem seems related to https://github.com/geonetwork/core-geonetwork/blob/1a780ac0d09f1a1df0cdbe23e513e8440c994227/core/src/main/java/org/fao/geonet/util/LogUtil.java#L74, as Quartz probably reuses threads and putIfNull does not update the value if a thread that had a set value has been reused. The other properties added to the ThreadContext are added using put instead. It is not clear why the log file name is added using putIfNull.

Checklist

[X] I have read the contribution guidelines
[X] Pull request provided for main branch, backports managed with label
[ ] Good housekeeping of code, cleaning up comments, tests, and documentation
[X] Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
[X] Clean commit messages, longer verbose messages are encouraged
[ ] API Changes are identified in commit messages
[ ] Testing provided for features or enhancements using automatic tests
[ ] User documentation provided for new features or enhancements in manual
[ ] Build documentation provided for development instructions in README.md files
[ ] Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

geonetwork / core-geonetwork