[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608514#comment-17608514 ]
ASF subversion and git services commented on LOG4J2-708: -------------------------------------------------------- Commit 432a851f0381a7bf9417a79ea9f9c64748b3020e in logging-log4j2's branch refs/heads/dependabot/maven/org.liquibase-liquibase-core-3.10.3 from Piotr P. Karwasz [ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=432a851f03 ] [LOG4J2-708] Improve `Log4jServletFilter` async behavior The `Log4jServletFilter` filter should run on all the threads a request is run. The current version ignores all async dispatches. > 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)