Hi,

I have fixed this in 2 ways...

Case #1:

log4j.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
    <appender name="LDAP" class="org.apache.log4j.DailyRollingFileAppender">
        <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
        <param name="Append" value="true"/>
        <param name="File" value="${jboss.server.log.dir}/ldap.log"/>
        <layout class="org.apache.log4j.PatternLayout">
            <param name="ConversionPattern" value="%d{dd.MM.yyyy HH:mm:ss.SSS} [%C{1}] - %m%n"/>
        </layout>
    </appender>
    <category name="com.xyz" additivity="false">
        <priority value="DEBUG"/>
        <appender-ref ref="LDAP"/>
    </category>
</log4j:configuration>

Add this a blank jar file and included inside EAR/lib. It worked like good.

Case #2:

Create a module in JBoss as modules and include the module in you application...

com
|------- xyz
          |------- log4j
                    |------- myapp
                              |------- main
                                        |------- module.xml
                                        |------- log4j.xml

module.xml

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.xyz.log4j.myapp">
    <resources>
        <resource-root path=""/>
    </resources>
    <dependencies>
        <module name="org.apache.log4j"/>
    </dependencies>
</module>

And in your EAR/WAR, include your log4j custom module dependency... like below....

<jboss-deployment-structure>
    <deployment>
        <dependencies>
            <module name="com.xyz.log4j.myapp" />
        </dependencies>
        <!-- Exclusions allow you to prevent the server from automatically adding some dependencies -->
        <exclusions>
            <module name="org.apache.log4j"/>
            <module name="org.slf4j" />
            <module name="org.apache.commons.logging"/>
            <module name="org.log4j"/>  
            <module name="org.jboss.logging"/>
        </exclusions>
    </deployment>
    <sub-deployment name="myapp.jar">
        <dependencies>
            <module name="com.xyz.log4j.myapp" />
        </dependencies>
        <exclusions>
            <module name="org.apache.log4j"/>
            <module name="org.slf4j" />
            <module name="org.apache.commons.logging"/>
            <module name="org.log4j"/>  
            <module name="org.jboss.logging"/>
        </exclusions>
    </sub-deployment>
    <sub-deployment name="myapp.war">
        <dependencies>
            <module name="com.xyz.log4j.myapp" />
        </dependencies>
        <exclusions>
            <module name="org.apache.log4j"/>
            <module name="org.slf4j" />
            <module name="org.apache.commons.logging"/>
            <module name="org.log4j"/>  
            <module name="org.jboss.logging"/>
        </exclusions>
    </sub-deployment>
    <sub-deployment name="myappPortal.war">
        <dependencies>
            <module name="com.xyz.log4j.myapp" />
        </dependencies>
        <exclusions>
            <module name="org.apache.log4j"/>
            <module name="org.slf4j" />
            <module name="org.apache.commons.logging"/>
            <module name="org.log4j"/>  
            <module name="org.jboss.logging"/>
        </exclusions>
    </sub-deployment>  
</jboss-deployment-structure>

Both worked excellent and In case 2, you can change logging level without touching application deployment.

If you want separate log files for each jar and war, still you create one more logging module and add dependency on the deployment structure xml.

Good luck buddies...

Jain,

Sorry for the late reply.

You may not need to restart JBoss. But, you may need to redeploy the application.

I hope, this helps.