The point of the testWarCommonsLoggingLog4jOverrides was to validate that the commons logging log4j factory does not bind its factory at the server class loader level and prevent resolution of the war local configuration from being used. If the upgraded commons logging is also not working then I guess it does need patching as well, but I thought it was supposed to work correctly for this scenario. The patched commons logging is in cvs.forge.jboss.com:/cvsroot/jboss under the module apache/commons-logging. http://fisheye.jboss.org/browse/JBoss/apache/commons-logging Dimitris Andreadis wrote: > We upgraded commons-logging in Branch_4_2 to v1.1 > http://jira.jboss.com/jira/browse/JBAS-2823 > > Now I see in the testsuite > org.jboss.test.classloader.test.ScopingUnitTestCase failing > (testWarCommonsLoggingLog4jOverrides), I believe due to not using a > patched commons-logging. > > I guess we have to patch v1.1 as well, like in here: > http://jira.jboss.com/jira/browse/JBAS-3128 > > I looked in the repository put I can't find the sources from the > previous patch. > > Where are they?