[
https://issues.apache.org/jira/browse/LOG4J2-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georgios Mournos updated LOG4J2-2439:
-------------------------------------
Description:
I upgraded from log4j-core-2.8.2 to log4j-core-2.11.1 and stacktraces in the
logs got very long. My xEx\{3} pattern is not working anymore.
Seems that when ExtendedThrowablePatternConverter calls ThrowableProxy, it does
not pass the number of lines to restrict the stacktrace.
was:
I upgraded from log4j-core-2.8.2 to log4j-core-2.11.1 and stacktraces in the
logs got very log. My xEx\{3} patter is not working anymore.
Seems that when ExtendedThrowablePatternConverter calls ThrowableProxy, it does
not pass the number of lines to restrict the stacktrace.
> xEx{n} broken- Stacktraces are not limited by size - on
> ExtendedThrowablePatternConverter
> -----------------------------------------------------------------------------------------
>
> Key: LOG4J2-2439
> URL: https://issues.apache.org/jira/browse/LOG4J2-2439
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.11.1
> Reporter: Georgios Mournos
> Priority: Major
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> I upgraded from log4j-core-2.8.2 to log4j-core-2.11.1 and stacktraces in the
> logs got very long. My xEx\{3} pattern is not working anymore.
> Seems that when ExtendedThrowablePatternConverter calls ThrowableProxy, it
> does not pass the number of lines to restrict the stacktrace.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
