That feature looks like it was introduced with LOG4J2-1923. That issue as marked as being fixed in Log4j 2.9.0. Unfortunately, I don’t see that issue in the manual change log so whoever committed it must have missed documenting it there.
Ralph > On Mar 16, 2018, at 7:56 AM, Fröstl, Christian > <christian.froe...@accenture.com> wrote: > > Hi everybody, > > I just tried to use the property stacktraceAsString in JSONLayout, but I > always get the following error: > ERROR JSONLayout contains an invalid element or attribute "stacktraceAsString" > > We are using log4j2 2.7, but I cannot find any changelog where this option > was introduced. Can anybody help me with this? > > Thanks and greetings, > Christian > > > ________________________________ > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise private information. If you have received it in > error, please notify the sender immediately and delete the original. Any > other use of the email by you is prohibited. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org