[
http://jira.qos.ch/browse/LBCLASSIC-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10959#action_10959
]
Wascally Wabbit commented on LBCLASSIC-20:
------------------------------------------
This issue has been closed but the ORIGINAL poster's request for AsyncAppender
was not addressed (the second poster linked generic AsyncAppender to
compression for whatever reason and looks like Ceki was addressing this poster
when he closed the issue).
At work,I was *this* (little space) close to recommending a migration from
log4j/jul/jcl to slf4j+logback but the lack of an AsyncAppender as the original
poster noted is a significant issue for use in production. We have many large
applications (by usage) and custom log4j appenders that will migrate
beautifully *iff* we also had AsyncAppender.
So why the lack of an async decorator? Does anyone really use custom
database/jms appenders without this in production for high volume?
At this point, even if you've got something "internal" I'll take it!
Thanks,
WW
> Implement AsyncAppender
> -----------------------
>
> Key: LBCLASSIC-20
> URL: http://jira.qos.ch/browse/LBCLASSIC-20
> Project: logback-classic
> Issue Type: Improvement
> Components: Other
> Affects Versions: unspecified
> Environment: Operating System: Windows
> Platform: PC
> Reporter: Anders Wallgren
> Assignee: Logback dev list
> Priority: Minor
> Fix For: 0.9.10
>
>
> Being able to write log files in the background is a requirement for
> production deployments of anything we would write on top of logback.
> Bonus points for including a feature to periodically flush the output.
--
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
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
