[jboss-jira] [JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations
[
https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGMGR-154:
--------------------------------------
From the forum post:
{quote}
2017-05-29 11:01:48 Commons Daemon procrun stderr initialized
LogManager error of type OPEN_FAILURE: Unable to rotate log file
java.nio.file.FileSystemException: C:\wildfly-9.0.2.Final\standalone\log\server.log ->
C:\wildfly-9.0.2.Final\standalone\log\server.log.1: The process cannot access the file
because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:387)
at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287)
at java.nio.file.Files.move(Files.java:1395)
{quote}
Log rotations should be more resilient to failed rotations
----------------------------------------------------------
Key: LOGMGR-154
URL: https://issues.jboss.org/browse/LOGMGR-154
Project: JBoss Log Manager
Issue Type: Bug
Reporter: James Perkins
If a failure occurs while rotating a file the file handler will stop working. The file
handler should instead report the failed rotation, but keep allowing messages to be
written.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)