[
https://issues.apache.org/jira/browse/LOG4J2-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-452.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-rc1
The rest of this has been fixed with r1561958, which adds a {{ServletContext}}
parameter for disabling auto-initialization. A separate commit tomorrow will
provide several updates to Log4j's web app documentation.
> 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
> Assignee: Nick Williams
> Priority: Critical
> Fix For: 2.0-rc1
>
> Attachments:
> 0001-Add-LOGGER_CONTEXT_ATTRIBUTE-to-LoggerContext.patch,
> 0002-Add-async-support-to-Log4jServletFilter.patch, log4-servlet-test.zip,
> patch_async.diff
>
>
> 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.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
