Hi Volkan,
Sorry I haven’t found time to look into this. Let me spend some time
tomorrow and get back to you
On Thu, Dec 17, 2020 at 2:22 AM Volkan Yazıcı
wrote:
> Hey Varun! Were you able to figure out the problem? Did you have any
> progress?
>
> On Sun, Dec 13, 2020 at 9:47 PM Volkan Yazıcı
Hey Varun! Were you able to figure out the problem? Did you have any
progress?
On Sun, Dec 13, 2020 at 9:47 PM Volkan Yazıcı
wrote:
> Varun, would you mind sharing the logger line causing this
> problem, please? That is, is it *logger.error("foo", exception)* or
> *logger.error(exception)*? Woul
Varun, would you mind sharing the logger line causing this problem, please?
That is, is it *logger.error("foo", exception)* or *logger.error(exception)*?
Would you share the "exception" too?
Assuming you can reproduce this locally, the best way to debug this is to
put a breakpoint into both of the
Hello Volkan,
Thanks for writing the test case.
So when I run the test case I am seeing what you see as well. Additionally
I checked out the `rel/2.14.0` tag and still wasn't able to reproduce the
problem.
I then thought of simplifying my log4j2.xml file and removed some Rewrite
filters, changed
Hello Varun,
Thanks for the detailed report. Though I still fail to reproduce the issue.
"message" resolver doesn't have an "includeStackTrace" configuration
option, though I can see where you are coming from. It is unfortunately a
leftover in the documentation. I will fix it in the manual. Your
I'm trying to use JSON Template Layout and can't figure out why is the
"message" field contain the full stack trace and why aren't some exception
resolvers working. They are probably connected. Adding
"includeStackTrace": false to the message resolver didn't help.
I've attached my log output, the
