[jboss-jira] [JBoss JIRA] (LOGMGR-161) AsyncHandler is always creating a stacktrace dump

[Tomas Hofman (JIRA)]

     [ https://issues.jboss.org/browse/LOGMGR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Hofman updated LOGMGR-161:
--------------------------------
    Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/129, https://github.com/jboss-logging/jboss-logmanager/pull/130  (was: https://github.com/jboss-logging/jboss-logmanager/pull/129)


> AsyncHandler is always creating a stacktrace dump
> -------------------------------------------------
>
>                 Key: LOGMGR-161
>                 URL: https://issues.jboss.org/browse/LOGMGR-161
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.1.0.Alpha1
>            Reporter: Koen Janssens
>            Assignee: James Perkins
>
> I have noticed that when introducing an AsyncHandler for logging, all log statement are copied before being put on the queue and as part of that copy a complete stack dump is done. 
> This might be useful if the stack info is used by a downstream formatter (eg for line number identification), but even if the line numbers are not used anywhere, this still happens. 
> I think this behavior should be at least optional. 
> Source Location: org.jboss.logmanager.ExtLogRecord#copyAll



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)