You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Andrei Ivanov (JIRA)" <ji...@apache.org> on 2018/08/22 07:46:00 UTC
[jira] [Created] (LOG4J2-2417) NullPointerException without any
`requestContext` attributes
Andrei Ivanov created LOG4J2-2417:
-------------------------------------
Summary: NullPointerException without any `requestContext` attributes
Key: LOG4J2-2417
URL: https://issues.apache.org/jira/browse/LOG4J2-2417
Project: Log4j 2
Issue Type: Bug
Components: Log4j-Audit
Reporter: Andrei Ivanov
The Log4j-Audit project page indicates this as the place to file tickets, but I don't see the 1.0.0 version for it.
Investigating the use of the project, I started with a basic `catalog.json`, with just an event and 2 attributes, both with {{requestContext = false}}.
{noformat}
java.lang.NullPointerException
at org.apache.logging.log4j.audit.LogEventFactory.validateContextConstraint(LogEventFactory.java:385)
at org.apache.logging.log4j.audit.LogEventFactory.validateContextConstraints(LogEventFactory.java:380)
at org.apache.logging.log4j.audit.LogEventFactory.access$400(LogEventFactory.java:57)
at org.apache.logging.log4j.audit.LogEventFactory$AuditProxy.invoke(LogEventFactory.java:263)
{noformat}
As far as I understand, request context attributes are not required.
??While usage of a RequestContext is not required, the use of one should be considered a best practice.??
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)