[ http://jira.qos.ch/browse/LBCLASSIC-175?page=com.atlassian.jira.plugin.syste... ] Torsten Juergeleit edited comment on LBCLASSIC-175 at 1/2/10 12:36 AM: ----------------------------------------------------------------------- Please keep LogEvent.prepareForDeferredProcessing()s current behavior of only preparing the "cheap" stuff like thread name and MDC. The "expensive" stuff (mainly the caller data) can be easily prepared by calling LogEvent.getCallerData() if really wanted. This is what the suggested implementation of an AsyncAppender attached to LBCLASSIC-177 is currently doing. Here the preparation of the caller data is only be done if requested by the user via configuration. was (Author: tjuerge): Please keep LogEvent.prepareForDeferredProcessing()s current behavior of only preparing the "cheap" stuff like thread name and MDC. The "expensive" stuff (mainly the caller data) can be easily prepared by calling LogEvent.getCallerData() if really wanted. This is what the suggested implementation of an AsyncAppender attached to http://jira.qos.ch/browse/LBCLASSIC-177 is currently doing. Here the preparation of the caller data is only be done if requested by the user via configuration.
ILoggingEvent prepareForDeferredProcessing does not include callerDataArray ---------------------------------------------------------------------------
Key: LBCLASSIC-175 URL: http://jira.qos.ch/browse/LBCLASSIC-175 Project: logback-classic Issue Type: Bug Components: layout Reporter: Konstantin Alexandrov Assignee: Logback dev list
I've implement asynchronous file appender, and enqueue events, but %caller pattern can not be used in the case of deferred processing becouse caller information is losed. My suggestion is to create Throwable object in prepareForDeferredProcessing
-- 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