[ http://issues.apache.org/jira/browse/LOG4NET-86?page=comments#action_12424357 ] Tal G commented on LOG4NET-86: ------------------------------
Nicko - I have two problems when using CountDirection=0. 1. For example if file.2 is locked, then when rolling, the information in file.1 will be lose. 2. I am having some cases when it takes too much time to roll, and I am having a soft real time environment. About the decimal - 1. You are right that decimal max value is enough, but we are having some relations with other companies that give certification to our applications, and they try to check all the extreme cases such as this. 2. We can overcome on the problem of moving to 0, we can add some code than deal with this. > 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
