The rotating file handlers use File.moveTo() which is noted in the JavaDoc as being highly implementation dependent. One example of this is that on Linux it will replace an existing target, but on Windows it will fail when doing that. A consequence of this is that if the periodic rotating file handler re-uses a file name, e.g. with a suffix only containing the date and not month or year, it will throw an exception, and continue logging to the same file. This can be fixed by using Files.move() with the option to replace the target file.
Posted PR to backport to the jboss-logmanager 1.5 branch, https://github.com/jboss-logging/jboss-logmanager/pull/90. If accepted, this bug can be fixed by upgrading to the next release.
A work-around for this bug is to use a file suffix with more data, such as the much more common yyyy-MM-dd.
Since the 1.5 logmanager stream relies on Java 6 the 2.x branch fix won't work. We'll need to first delete the file, then rename it to replicate the move/replace.
PR sent : https://github.com/jboss-logging/jboss-logmanager/pull/91
Verified with EAP 6.4.10.CP.CR1
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.