1 Reply Latest reply on Apr 6, 2015 1:45 PM by jamezp

    JBoss 6.3 using application log4j.xml

    jason.major

      I am moving an application from JBoss 4 to JBoss 6.3 and have worked out how to get the internal log4j configuration to be used in place of the JBoss Log manager by creating the following deployment structure file.  I spent a good bit of time working out that the exclusion needed to happen in the subdeployment as well as the main deployment...

       

      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">

           <deployment>

                <exclusions>

                     <module name="org.apache.log4j" />

                </exclusions>

           </deployment>

           <sub-deployment name="application.war">

                <exclusions>

                     <module name="org.apache.log4j" />

                </exclusions>

           </sub-deployment>

      </jboss-deployment-structure>

       

      What I would like to do is be able to control the name of the log4j.xml file JBoss looks for in the ear / war on startup to some other file name.  My application has a customized name and I would rather not rename the file if it is not completely necessary.  Is there a command or option to change log4j.xml to mycustomname.xml?

       

      Any help would be greatly appreciated.

       

      Regards,

       

      Jason

        • 1. Re: JBoss 6.3 using application log4j.xml
          jamezp

          If you're excluding the org.apache.log4j module then configuration is up to do the log4j library you bundle in your deployment. You'd have to look at the log4j documentation in order to determine how to use a different configuration file name.

           

          --

          James R. Perkins