[jira] [Resolved] (LOG4J2-2012) No compression when using a separate drive in Linux

["Gary Gregory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory resolved LOG4J2-2012.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.9

Fixed by [LOG4J-2016]. Please verify and close this ticket.

> No compression when using a separate drive in Linux
> ---------------------------------------------------
>
>                 Key: LOG4J2-2012
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2012
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7
>         Environment: Unix
>            Reporter: Benjamin Jaton
>             Fix For: 2.9
>
>
> When setting up the filePattern of a RollingFileAppender pointing to a different FS than the fileName, the file gets moved but not compressed:
> In this example, /usr/local and /archives are not on the same FS:
> {code}2017-08-11 14:34:33,632 pool-8-thread-1 TRACE DefaultRolloverStrategy.purge() took 15.0 milliseconds 
> 2017-08-11 14:34:33,643 pool-8-thread-1 DEBUG RollingFileManager executing synchronous FileRenameAction[/usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log, renameEmptyFiles=false] 
> 2017-08-11 14:34:33,646 pool-8-thread-1 ERROR Unable to move file /usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log: java.nio.file.AtomicMoveNotSupportedException /usr/local/app/logs/app.log -> /archives/logs/app-2017-08-11_14-34-33.log: Invalid cross-device link 
> 2017-08-11 14:34:33,736 pool-8-thread-1 TRACE Renamed file /usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log using copy and delete{code}
> Also reported here:
> https://stackoverflow.com/questions/43179979/log4j2-rollingfileappender-invalid-cross-device-link



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)