[
https://issues.apache.org/jira/browse/LOG4J2-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandra Sekhar Kakarla updated LOG4J2-512:
------------------------------------------
Affects Version/s: 2.0-beta8
> Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while automatically
> starting, and configurable to initialize and de-initialize loggers from the
> code
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-512
> URL: https://issues.apache.org/jira/browse/LOG4J2-512
> Project: Log4j 2
> Issue Type: Sub-task
> Components: Configurators, Core, Documentation, Filters
> Affects Versions: 2.0-beta8, 2.0-beta9
> Reporter: Chandra Sekhar Kakarla
> Labels: asynchronous, configuration, destroy, filters,
> initialization, listener, log4j2, log4j2.xml, restart, servlet,
> servlet-context
> Original Estimate: 466h
> Remaining Estimate: 466h
>
> Async servlet (async-supported=true) using with log4j2 breaks the async chain
> because it does not support async.
> All element in the chain must support async in order to use async.
> Implementation is required to support async servlets(async-supportd=true) it
> may be automatic or configurable initialization.
> Initialization and de-initialization of the logger must be configurable in
> the java code/config files, to re-load the logger with different properties,
> that will help the application to reduce re-start burden when it need to use
> different properties.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
