Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1853

Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override.

    Details

    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration

      Description

      The default logging configuration location mechanism of log4j will find the server conf/log4j.xml file. One simple isolation step is to rename this file conf/jboss-log4j.xml since we do not rely on the default logging configuration location mechanism of log4j. The next level of isolation is to actually create a unique LoggerRepository for use by the jboss Logger in the Log4jService. The concern is that components like jgroups, hibernate, tomcat, etc. using commons logging will fail to pickup the Log4jService LoggerRepository. We probably need to configure commons logging as well from the Log4jService with a flag that can disable this.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dimitris Dimitris Andreadis
                  Reporter:
                  starksm64 Scott Stark
                • Votes:
                  5 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: