logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Communier (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-452) Log4j2 should not automatically start in Servlet 3.0
Date Thu, 14 Nov 2013 15:55:22 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Anthony Communier updated LOG4J2-452:

    Attachment: log4-servlet-test.zip

I try to make a patch in order to support async in the filter. But it's not enough.

I have attched an exemple of test servlet

> 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
>         Attachments: 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message