[ https://issues.apache.org/jira/browse/LOG4J2-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226973#comment-13226973 ]
Ralph Goers commented on LOG4J2-44: ----------------------------------- Log4j2 was moved from my experimental branch to a proper trunk at https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk. Since your post in October the Flume appender was also broken out into a subproject (actually two - one for Flume 0.9.4 and the other for Flume 1.0). I see from the output in your link above you have 9 unit test failures. I'd appreciate it if you could download the latest source and run the build again and then create a new Jira issue for those and attach the output as well as the output from each of the unit tests (you will find them in log4j2-core/target/surefire-reports/ with the file name matching the full class name and an extension of .txt). I'd like to see what you did for the Async appender. I've contemplated creating one. I'm sure it would be fairly easy to add a listener to the rolling file appender. I will look into that. The rolling file appender will already zip if the filePattern has a .zip extension. The current documentation is temporarily at http://people.apache.org/~rgoers/log4j2. That will move to the main Logging web site with the first release of Log4j2. (After looking at the documentation I notice that it doesn't mention that it will compress to zip or gzip if the file extension is specified in the filePattern. I will fix that). If you specify a very large number for "max" on the RolloverStrategy then none of the log files will be deleted. Log4j2 currently does everything you are mentioning except a) it doesn't encrypt and b) buffering is handled by whatever FileOutputStream does. Again, these can be tailored if required. > log4j java date wise log every X MB > ----------------------------------- > > Key: LOG4J2-44 > URL: https://issues.apache.org/jira/browse/LOG4J2-44 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders > Reporter: Tushar > Priority: Minor > > a log roll over that makes a new file every x MB/ KB but the current file is > archived with a full date-time--random-int-to-make- unique stamp > so if the file is myProj_A.log after x MB is renamed to > myProj_A_2010_09_10_02_48_02_XX34334.log (year-month-day- time ...) and so on > Is there a pattern/ property to do this already? > can see http://www.simonsite.org.uk/ and > http://www.simonsite.org.uk/javadoc/org/apache/log4j/appender/TimeAndSizeRollingAppender.html > here the code is a little mixed up (we want test and real code in seperate > src roots) - and not sure if it works completely but it says it does. but it > has our requirements. > Code should write out buffer in bits instead of blocking for a long time > emptying full buffer when buffer is full Or is that done by nio ? > build and run script to test with params to control logging, number of > threads, amount of data logged so we can see that the logs are rolling as > planned we want the final roller to roll every day but can keep that as hour > and minute params (so final will be 24 hours and 0 minutes, but for testing > can be 5 minutes only, similarly size can be in KB) also need format of file > name with prefix for folder so the root log folder can be c:\log then we > specify the dynamic sub folder like yyyy\mm\dd meaning make sub folders for > current year, inside that for month and inside that for day and finally the > file name format with a prefix like myApp_{yyyy_mm_dd_HH_II_SS) and post fix > so the final file will be in folder (example) > C:\log\2010\10\29\myApp_2010_10_29_14_34_22_randXYZ.txt where randXYZ stand > for some random text that is added to make the file name unique (as required > or can use java inbuilt getTempFile function ...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org