[
https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFCORE-482:
--------------------------------------
Thanks for the detailed information [~marlowa42]. That CVE is fixed in WildFly as well see
https://github.com/jboss-logging/log4j-jboss-logmanager/pull/15.
For log4j we actually use a fork that routes through the JBoss Log Manager. The main
reason for including log4j is for legacy applications. That said we should make adding
log4j2 support higher priority. I do have an implementation that does work with the JBoss
Log Manager, I just have had time to work on the integration and testing of it.
Add log4j2 support for WildFly
------------------------------
Key: WFCORE-482
URL:
https://issues.jboss.org/browse/WFCORE-482
Project: WildFly Core
Issue Type: Task
Components: Logging
Environment: Spring 3, Hibernate, Wicket, JBoss AS7
Reporter: Amarkanth Ranganamayna
Assignee: James Perkins
Priority: Major
I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support
flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7
to use log4j2.
Looks like Jboss AS7 by default use log4j 1.x
Are you guys already working on using log4j2 ?
If NOT, can you please suggest how to configure Jboss AS7 such that it picks up
"log4j2.xml" file and doesn't use its own logging.
Thanks,
Amar
--
This message was sent by Atlassian Jira
(v7.13.8#713008)