You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2014/07/11 03:48:04 UTC
[jira] [Updated] (LOG4J2-708) Servlet filter claims to support
async but doesn't use AsyncContext
[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker updated LOG4J2-708:
-------------------------------
Issue Type: Question (was: Bug)
> Servlet filter claims to support async but doesn't use AsyncContext
> -------------------------------------------------------------------
>
> Key: LOG4J2-708
> URL: https://issues.apache.org/jira/browse/LOG4J2-708
> Project: Log4j 2
> Issue Type: Question
> Affects Versions: 2.0-rc2
> Environment: Servlet 3.0 (Tomcat 7, Jetty 8) or higher
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> In log4j-web, when the ServletContainerInitializer adds the Log4j Filter, it sets the asyncSupported property to true. However, it's still a synchronous Filter.
> A separate asynchronous Filter should be made for Servlet 3.x support that doesn't break Servlet 2.x.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org