[ http://issues.apache.org/jira/browse/LOG4NET-86?page=comments#action_12424446 ] Nicko Cadell commented on LOG4NET-86: -------------------------------------
I agree that adding code to correctly handle the wrap around condition would be better than just expanding the number space by switching to a decimal type. Would you be able to contribute a patch to support rolling the curSizeRollBackups back round to 0? > 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
