Anthony Communier created LOG4J2-452:
----------------------------------------
Summary: Log4j2 should not automatically start in Servlet 3.0
Key: LOG4J2-452
URL: https://issues.apache.org/jira/browse/LOG4J2-452
Project: Log4j 2
Issue Type: Bug
Components: Filters
Affects Versions: 2.0-beta9
Reporter: Anthony Communier
Priority: Critical
When using async servlet (async-supported=true inweb.xml), log4j2 breaks the
async chain because it does not support async. All element in the chain must
support async in order to use async. Using Log4j2 in web context lead to be
unable to use async.
Be aware that async mecanism is more complicated than just intercept the chain
before and after the handling of the request (thing that could be done in sync
context). When using async mecanism web container threads can be used when the
start method is invoked on AsyncContext and there are no way to intercept this
systematically.
So I m not sure that it's a good idea to automatically intercept request with
a filter.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
