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 "Chandra Sekhar Kakarla (JIRA)" <ji...@apache.org> on 2014/01/25 16:08:37 UTC
[jira] [Created] (LOG4J2-512) Log4j2 need to support Asynchronous
Servlets/ Servlet 3.0 while automatically starting, and configurable to
initialize and de-initialize loggers from the code
Chandra Sekhar Kakarla created LOG4J2-512:
---------------------------------------------
Summary: 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-beta9
Reporter: Chandra Sekhar Kakarla
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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org