Round initialTime in RollingFileManager

Caching of filesystem timestamps (at least in ext4 on Linux) results in non-accurate creation timestamps.

Thus, let's round it to the second.

Rounding is also applied for the lastModified time, but I'm not sure whether it's needed there.

Fixes #3068.

Author: kelunik

log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/RollingFileManager.java

@@ -918,15 +918,19 @@ private static long initialFileTime(final File file) {
                 final FileTime fileTime = attrs.creationTime();
                 if (fileTime.compareTo(EPOCH) > 0) {
                     LOGGER.debug("Returning file creation time for {}", file.getAbsolutePath());
-                    return fileTime.toMillis();
+
+                    // See https://github.com/apache/logging-log4j2/issues/3068
+                    return Math.round(fileTime.toMillis() / 1000d) * 1000;
                 }
-                LOGGER.info("Unable to obtain file creation time for " + file.getAbsolutePath());
+                LOGGER.info("Unable to obtain file creation time for {}", file.getAbsolutePath());
             } catch (final Exception ex) {
-                LOGGER.info("Unable to calculate file creation time for " + file.getAbsolutePath() + ": "
-                        + ex.getMessage());
+                LOGGER.info(
+                        "Unable to calculate file creation time for {}: {}", file.getAbsolutePath(), ex.getMessage());
             }
         }
-        return file.lastModified();
+
+        // See https://github.com/apache/logging-log4j2/issues/3068
+        return Math.round(file.lastModified() / 1000d) * 1000;
     }
 
     private static class EmptyQueue extends ArrayBlockingQueue<Runnable> {