2018-06-09 13:56 GMT+02:00 Jaikiran Pai :
>
> On 09/06/18 5:22 PM, Gintautas Grigelionis wrote:
>
>>
>> Thanks for review, Jaikiran. You're correct, that is the proposed
>> solution,
>> adding a separator
>> (a newline followed by an exception name for clarity -- mind that
>> exception
>> is logge
On 09/06/18 5:22 PM, Gintautas Grigelionis wrote:
Thanks for review, Jaikiran. You're correct, that is the proposed solution,
adding a separator
(a newline followed by an exception name for clarity -- mind that exception
is logged only in debug mode).
The exception class name would already be
2018-06-09 13:31 GMT+02:00 Jaikiran Pai :
> For easy reference, the bug in discussion is this one
> https://bz.apache.org/bugzilla/show_bug.cgi?id=62324
>
>
> On 09/06/18 12:38 AM, Gintautas Grigelionis wrote:
>
>> Namely, a stack trace of the exception is logged (in debug mode only)
>> without an
For easy reference, the bug in discussion is this one
https://bz.apache.org/bugzilla/show_bug.cgi?id=62324
On 09/06/18 12:38 AM, Gintautas Grigelionis wrote:
Namely, a stack trace of the exception is logged (in debug mode only)
without any separator from the preceding message. While it seems t
I was advised to solicit opinions regarding the change introduced as a fix
for the abovementioned issue. It concerns how an event that has both a
message and an exception is logged.
Namely, a stack trace of the exception is logged (in debug mode only)
without any separator from the preceding messa
