[jira] [Work logged] (LOG4J2-3627) PatternLayout: %xEx{ [ "short" | depth]} not working

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-3627?focusedWorklogId=858699&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858699 ]

ASF GitHub Bot logged work on LOG4J2-3627:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Apr/23 10:59
            Start Date: 24/Apr/23 10:59
    Worklog Time Spent: 10m 
      Work Description: hein4daddel commented on PR #1137:
URL: https://github.com/apache/logging-log4j2/pull/1137#issuecomment-1519908835

   Will this fix be available in the next release? (haven't found it in 2.20.0)




Issue Time Tracking
-------------------

    Worklog Id:     (was: 858699)
    Time Spent: 0.5h  (was: 20m)

> PatternLayout: %xEx{ [ "short" | depth]} not working
> ----------------------------------------------------
>
>                 Key: LOG4J2-3627
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3627
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Layouts
>    Affects Versions: 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.13.1, 2.13.2, 2.14.0, 2.13.3, 2.14.1, 2.15.0, 2.16.0, 2.17.1, 2.17.0, 2.12.3, 2.12.2, 2.18.0, 2.12.4, 2.17.2, 2.19.0
>            Reporter: Thorsten Heit
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> According to the documentation the patterns {{{}%xEx{short{}}}} or {{{}%xEx{<num>{}}}} should limit the number of lines of a stack trace that is logged. This doesn't work; instead, the complete stack trace is logged (always!). This is in contrary to the patterns {{%ex}} or {{%rEx}} where this works.
> In commit 9ff63b2e50be754ae394feda2c33d9e64fd0ab3a (2018-01-25) a change was implemented because of LOG4J2-2195 (according to the commit message) that removed the option of limiting the number of lines to output.
> Therefore all versions since 2.11.0 should be affected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)