[ http://jira.qos.ch/browse/LBCLASSIC-176?page=com.atlassian.jira.plugin.syste... ] Konstantin Alexandrov commented on LBCLASSIC-176: ------------------------------------------------- I'm also worry about issue you describe, and choose ArrayBlockingQueue instead of Linked or Concurrent queue. I'm sorry, but your logic, from my point of view, is too complicated and may have lot of heuristics and raise conditions. ArrayBlockingQueue will block on put and logger behaviour will same as for RollingFileAppender. Also, this queue does not allocate new nodes to store events and use pre allocated circular buffer, which is match more fast than linked list and no need to be volatile or so, means no copying of variables from global memory to thread memory. I think such behaviour is predictable and easy to find weak chain using profiling or so. About events lose. I'm developer for financial systems, so for me, lose of events is crime ;) I'm interested for complete development of this part, but primary is using for my company applications
Asynchronous File appender --------------------------
Key: LBCLASSIC-176 URL: http://jira.qos.ch/browse/LBCLASSIC-176 Project: logback-classic Issue Type: New Feature Components: appender Reporter: Konstantin Alexandrov Assignee: Logback dev list Attachments: asynch.zip, AsynchRollingFileAppender.java, AsynchRollingFileAppender.java
I implement asynch rolling file appender for my application, the reason is to decrease logging time in time critical part of application. This logger save up to 2 time logging time and decrease total IO concurrency. If you found this appender usable, then please include to distribution. Thanks
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira