|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
This just happened this morning in my production environment, and it was caused by multiple processes (different JVMs) logging to a file in the same directory. The parent directory in question did not exist, and all processes were started at the same time, running in parallel on multiple CPU cores. So while it may not happen within multiple threads of the same JVM, it does happen definitely when multiple processes are involved.
Can you please look to fix? This has been verified with Logback 1.0.13 the code still has this race condition
Ignoring the return value of mkdirs() is the correct approach, per the supplied patch