[
https://issues.apache.org/jira/browse/LOG4J2-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971468#comment-14971468
]
Hai-Dang Pham commented on LOG4J2-1173:
---------------------------------------
I am doubtful. When we switch out only the Log4j's jars from 2.4/2.4.1 to 2.3
from our application on the same Linux host everything work. With 2.4/2.4.1
the archiving file does get created in the remote location but it can't be
written into (always stay at size 0), the running logging file keep increasing
well pass the set size limit (e.g. set by SizeBasedTriggeringPolicy).
> ERROR Unable to rename file in version 2.4 and 2.4.1
> ----------------------------------------------------
>
> Key: LOG4J2-1173
> URL: https://issues.apache.org/jira/browse/LOG4J2-1173
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.4
> Environment: Linux
> Reporter: Hai-Dang Pham
>
> When using RollingAppender with version 2.4 and 2.4.1 with the archiving
> directory mapped to a remote Linux host. We get the following error:
> {quote}
> 2015-10-22 18:33:33,082 Thread-1 ERROR Unable to rename file
> /opt/local/log/servicedeamon_124.log to
> /home/remote/Logs/20151022/servicedeamon-20151022-13.log -
> /home/remote/Logs/20151022/servicedeamon-20151022-13.log
> {quote}
> This used to work in version 2.3. Looking at FileRenameAction.java, I see
> that the method copyFile(final File source, final File destination) has been
> modified extensively. Issue started happening when java.nio.file.Files were
> used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
