t;>>>> I created https://issues.apache.org/jira/browse/LOG4J2-1608
>>>>>
>>>>> Gary
>>>>>
>>>>> On Thu, Sep 22, 2016 at 8:22 AM, Matt Sicker wrote:
>>>>>
>>>>>> Oh that explains it, thanks for t
22 September 2016 at 10:21, Ralph Goers >>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>> PatternLayout defaults to implicitly add %ex or one of its variations to
>>>> your pattern if you don’t specify it. To disable exception logging you
>>>> have to use %n
> Oh that explains it, thanks for the info!
>>>>>
>>>>> On 22 September 2016 at 10:21, Ralph Goers >>>> > wrote:
>>>>>
>>>>>> PatternLayout defaults to implicitly add %ex or one of its variations
>>>>>>
s >> <mailto:ralph.go...@dslextreme.com>> wrote:
>>> PatternLayout defaults to implicitly add %ex or one of its variations to
>>> your pattern if you don’t specify it. To disable exception logging you have
>>> to use %noex.
>>>
>>> R
or one of its variations
>>>>> to your pattern if you don’t specify it. To disable exception logging you
>>>>> have to use %noex.
>>>>>
>>>>> Ralph
>>>>>
>>>>> On Sep 22, 2016, at 6:55 AM, Matt
>>>
>>>> Ralph
>>>>
>>>> On Sep 22, 2016, at 6:55 AM, Matt Sicker wrote:
>>>>
>>>> I usually don't even include %exception in my pattern layouts for some
>>>> reason, probably because of the double logging.
xception in my pattern layouts for some
>>> reason, probably because of the double logging. So I'd go with (1) as well.
>>>
>>> On 22 September 2016 at 02:59, Gary Gregory >> <mailto:garydgreg...@gmail.com>> wrote:
>>> Hi All,
>>>
>>> The method
>>> org.apache.loggin
uts for some
>>> reason, probably because of the double logging. So I'd go with (1) as well.
>>>
>>> On 22 September 2016 at 02:59, Gary Gregory
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> The method
>>>> org.apac
>> wrote:
>>
>> I usually don't even include %exception in my pattern layouts for some
>> reason, probably because of the double logging. So I'd go with (1) as well.
>>
>> On 22 September 2016 at 02:59, Gary Gregory > <mailto:garydgreg...@g
layouts for some
>> reason, probably because of the double logging. So I'd go with (1) as well.
>>
>> On 22 September 2016 at 02:59, Gary Gregory
>> wrote:
>>
>>> Hi All,
>>>
>>> The method
>>> org.apache.log
regory
> wrote:
>
>> Hi All,
>>
>> The method
>> org.apache.logging.log4j.web.appender.ServletAppender.append(LogEvent)
>> is defined as:
>>
>> @Override
>> public void append(final LogEvent event) {
>> servletContext.log(((AbstractStringLayout)
>&g
rn layouts for some
> reason, probably because of the double logging. So I'd go with (1) as well.
>
> On 22 September 2016 at 02:59, Gary Gregory <mailto:garydgreg...@gmail.com>> wrote:
> Hi All,
>
> The method
> org.apache.logging.log4j.web.appender.
I usually don't even include %exception in my pattern layouts for some
reason, probably because of the double logging. So I'd go with (1) as well.
On 22 September 2016 at 02:59, Gary Gregory wrote:
> Hi All,
>
> The method
> org.apache.logging.log4j.web.appender.ServletAp
Hi All,
The
method org.apache.logging.log4j.web.appender.ServletAppender.append(LogEvent)
is defined as:
@Override
public void append(final LogEvent event) {
servletContext.log(((AbstractStringLayout)
getLayout()).toSerializable(event));
}
Instead of:
@Override
14 matches
Mail list logo
