You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Ron Grabowski (JIRA)" <ji...@apache.org> on 2006/10/12 22:53:43 UTC
[jira] Commented: (LOG4NET-86) In RollingFileAppender when setting
CountDirection=1 and the curr size reach int.MaxValue
[ http://issues.apache.org/jira/browse/LOG4NET-86?page=comments#action_12441867 ]
Ron Grabowski commented on LOG4NET-86:
--------------------------------------
Does this issue describe a problem for real applications? It sounds like a very hypothetical edge case. On that note, can we continue to add extensions to the file name:
Log.2147483647.1
Log.2147483647.2
Log.2147483647.3
...
Log.2147483647.2147483647
Log.2147483647.2147483647.1
Log.2147483647.2147483647.2
Log.2147483647.2147483647.3
...
Log.2147483647.2147483647.2147483647
Log.2147483647.2147483647.2147483647.2147483647
...
There's an example with a directory containing ~8.5 million files :-/
> In RollingFileAppender when setting CountDirection=1 and the curr size reach int.MaxValue
> -----------------------------------------------------------------------------------------
>
> Key: LOG4NET-86
> URL: http://issues.apache.org/jira/browse/LOG4NET-86
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: All
> Reporter: Tal G
>
> In RollingFileAppender when setting CountDirection=1 and the curr size reach int.MaxValue the log4net
> 1. Open a new file with .-2147483648 extension. And stop deleting old files for example file with extension .2147483638.
> 2. When i restart my application, it start writing log on the file with .-2147483648 although the newest file is with extension .-2147483643.
> 3. etc.. many more bugs related to this issue
> I suggest that when the file extension reach int.MaxValue move to 0 again and continue properly deleting old files and opening new files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira