[jboss-jira] [JBoss JIRA] (LOGMGR-47) JBoss log4j is overridden by web application's log4j

[Rohan Jain (JIRA)]

     [ https://issues.jboss.org/browse/LOGMGR-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohan Jain updated LOGMGR-47:
-----------------------------

    Attachment: jboss-classloading.xml


jboss-classloading xml file used
                
> JBoss log4j is overridden by web application's log4j
> ----------------------------------------------------
>
>                 Key: LOGMGR-47
>                 URL: https://issues.jboss.org/browse/LOGMGR-47
>             Project: JBoss Log Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Rohan Jain
>            Assignee: David Lloyd
>              Labels: jboss
>         Attachments: jboss-classloading.xml
>
>
> Issue in JBoss 5.1. When the client application hits my web application, all the system out logs and jboss undeploy lines are getting printed in my webapplication logs instead of server logs. 
> I tried to add "<attribute name="CatchSystemOut">false</attribute>" in jboss-service.xml. It stopped logging the system out lines in the web app logs, but they are not logged even in server logs. The system outs were just seen on the console.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira