weblogic war 배포시 log4j 설정이 동작하지 않을때

대부분 tomcat에서 테스트/개발을 진행해도 충분합니다만,

특정WAS에서 테스트를 거치거나 종속적 기능을 사용할 경우가 있습니다.
log4j 설정이 weblogic12c 서버 배포후 적용되지 않을때,
실례로 로그파일크기가 심각한 수준으로 증가하여 서비스 응답이 느려지고,

프로세스가 hogging이나 stuck 상태에 빠진 경우가 있습니다.
아래 파일을 WEB-INF에 추가 후 배포해 보세요.

weblogic.xml

<!?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.5/weblogic-web-app.xsd">
    <wls:container-descriptor>
        <wls:prefer-web-inf-classes>false</wls:prefer-web-inf-classes>
        <wls:prefer-application-packages>
            <wls:package-name>org.slf4j</wls:package-name>
            <wls:package-name>org.apache.log4j</wls:package-name>
            <wls:package-name>org.apache.commons</wls:package-name>
            <wls:package-name>net.sf.log4jdbc</wls:package-name>
        </wls:prefer-application-packages>
        <wls:prefer-application-resources>
            <wls:resource-name>org/slf4j/impl/StaticLoggerBinder.class</wls:resource-name>
        </wls:prefer-application-resources>
    </wls:container-descriptor>
    <wls:weblogic-version>12.1.2</wls:weblogic-version>
    <wls:context-root>context-name</wls:context-root>
</wls:weblogic-web-app>