[jboss-jira] [JBoss JIRA] (WFLY-1037) Add log4j2 support for WildFly

James Perkins (JIRA) issues at jboss.org
Fri Jun 13 11:18:38 EDT 2014


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

James Perkins commented on WFLY-1037:
-------------------------------------

We don't use log4j as the log manager or anywhere in the core. The only thing I think we could do is just add a log4j2 dependency to deployments during the deployment process. What is it specifically you're looking for? Do you just want to configure your deployment with log4j2 or are you looking to use a log4j2 appender as a custom-handler?

> Add log4j2 support for WildFly
> ------------------------------
>
>                 Key: WFLY-1037
>                 URL: https://issues.jboss.org/browse/WFLY-1037
>             Project: WildFly
>          Issue Type: Clarification
>      Security Level: Public(Everyone can see) 
>          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
(v6.2.6#6264)


More information about the jboss-jira mailing list