You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2022/09/11 19:59:00 UTC

[jira] [Resolved] (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 ]

Piotr Karwasz resolved LOG4J2-708.
----------------------------------
    Resolution: Fixed

> 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: Improvement
>    Affects Versions: 2.0-rc2
>         Environment: Servlet 3.0 (Tomcat 7, Jetty 8) or higher
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Minor
>             Fix For: 2.19.1
>
>
> 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
(v8.20.10#820010)