Remko Popma created LOG4J2-250:
----------------------------------
Summary: (TBD) Only create ThrowableProxy if it is used in
configuration
Key: LOG4J2-250
URL: https://issues.apache.org/jira/browse/LOG4J2-250
Project: Log4j 2
Issue Type: Improvement
Components: Core
Affects Versions: 2.0-beta5
Reporter: Remko Popma
Background: during investigation of LOG4J2-245, several people raised
performance concerns regarding ThrowableProxy. This issue is to separate that
concern so that LOG4J2-245 can focus on resolving the EmptyStackException.
ThrowableProxy does quite a bit of expensive-looking work to find the JAR file
or directory where the class that threw the exception is located. This work is
done for every event that contains an exception.
However, this information is only used when the configuration contains either a
RootThrowablePattern {"rEx", "rThrowable", "rException" } or an
ExtendedThrowablePattern {"xEx", "xThrowable", "xException" }.
This JIRA is to analyse the performance cost of constructing a ThrowableProxy
and (if it is significant) investigate ways to make construction optional based
on the configuration. That is, only construct ThrowableProxy if the
configuration contains a pattern that will use this information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
