[jboss-jira] [JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13378533#comment-13378533 ] 

James Perkins commented on WFCORE-482:
--------------------------------------

I've actually got a project that will actually write log4j2 messages to the logging subsystem, https://github.com/jamezp/log4j2-jboss-logmanager. A new project could be created and added to WildFly without too much of a problem. 

The problem is I don't really know what users expect. If they include a log4j2 configuration file, then that will not be used. Things like async-loggers won't be used either.

I suppose the easiest approach is to just make the log4j2-jboss-logmanager an official project so logs are written via the logging subsystem. If users expect log4j2 to work with their own configuration they're going to have to exclude the dependencies provided by the server and handle it that way.

> 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: Optional
>
> 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.2.3#72005)