[logback-dev] [JIRA] Commented: (LBCLASSIC-175) ILoggingEvent prepareForDeferredProcessing does not include callerDataArray

Torsten Juergeleit (JIRA) noreply-jira at qos.ch
Sat Jan 2 17:02:33 CET 2010


    [ http://jira.qos.ch/browse/LBCLASSIC-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11484#action_11484 ] 

Torsten Juergeleit commented on LBCLASSIC-175:
----------------------------------------------

>From http://blogs.sun.com/jrose/entry/longjumps_considered_inexpensive :

The most costly part of exception processing on the JVM is creating the exception, not throwing it. Exception creation involves a native method named Throwable.fillInStackTrace, which looks down the stack (before the actual throw) and puts a whole backtrace into the exception object. It's great for debugging, but a terrible waste if all you want to do is pop a frame or two.

> 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

        


More information about the logback-dev mailing list