Composite configuration implies that you are merging multiple configuration
files. Yes, it would appear that the configuration being merged has one node
with no configuration under it.
If you only have a single configuration this shouldn’t happen.
Ralph
> On May 24, 2019, at 10:34 AM, Gaurav
Hi,
Getting NullPointerException in DefaultMergeStrategy class.
codeblock -
"if
(targetNode.getAttributes().get(NAME).equals(node.getAttributes().get(NAME))) "
Probable suspect is that I've developed an appender similar to failoverappender
and it does not contain any child nodes.
e.g.
Sta
On 2019/05/24 12:11:19, Apache wrote:
> The code you highlight is there to include the throwable converter if one is
> not specified. If you add your own throwable converter then handlesThrowable
> will be true and that code won’t be run.
>
> You can also hide the exception with %noex.
>
>
On 2019/05/24 11:14:25, Gaurav wrote:
>
>
> On 2019/05/22 15:36:11, "Carter Kozak" wrote:
> > Once you've implemented a LogEventPatternConverter which overrides
> > "handlesThrowable" to return true, you will also need to use that pattern
> > in the PatternLayout pattern. This can be a l
The code you highlight is there to include the throwable converter if one is
not specified. If you add your own throwable converter then handlesThrowable
will be true and that code won’t be run.
You can also hide the exception with %noex.
Under what circumstances do you want to hide the excepti
On 2019/05/22 15:36:11, "Carter Kozak" wrote:
> Once you've implemented a LogEventPatternConverter which overrides
> "handlesThrowable" to return true, you will also need to use that pattern in
> the PatternLayout pattern. This can be a little bit confusing since the
> pattern layout will a
On 2019/05/22 17:47:56, Ralph Goers wrote:
> PatternLayout isn’t really designed to use an alternate implementation of
> PatternParser. Why do you need one? A custom Layout wouldn’t normally use a
> PatternParser, only PatternLayout and you shouldn’t need to modify that
> either.
>
> Just
