[LOG4J2-512] Log4j2 need to support Asynchronous Servlets/ Servlet 3.0 while automatically starting, and configurable to initialize and de-initialize loggers

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta8, 2.0-beta9
• Fix Version/s: 2.0-rc1
• Component/s: Configurators, Core, Documentation, Filters
• Labels: asynchronous configuration destroy filters initialization listener log4j2 log4j2.xml restart servlet servlet-context
• Assignee: Nick Williams
• Reporter: Chandra Sekhar Kakarla
• Created: 25/Jan/14 15:06
• Updated: 29/Jan/14 06:18
• Resolved: 28/Jan/14 07:16

Description

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. ( this Issue may be dependent on the issue https://issues.apache.org/jira/browse/LOG4J2-270 )

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.