I checked classload scoping with 3.2.5 and 4.0 (default config). I also deployed the log4j.war from the example, the log data get logged in the server.log....... Same with JBoss 4.0
What happens is that Jboss seems to try some reflections and throws MethodNotFound Exceptions and ReflectionExceptions on the BaseModelMBean of org.apache.commons.modeler.
I have the Apache Commons and the log4j Jar's in my classpath (WEB-INF\LIB, an own logFactory with commons-logging.properties
and the log4j.properties in WEB-INF\Classes.
I read in another post about a bug in 3.2.5 where the classpath is at servlet init time not available, which you stated is fixed in 3.2.6RC1. Could that be the problem?
I packaged the log4j.war in an ear and got some more information
2004-09-27 09:52:45,598 WARN [org.jboss.deployment.DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig (repositoryName: log4j.test:loader=log4j.war, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
did you get any solution for your poblem? Since I have the same problem, I would be glad to know how you solved it.
I am trying to set up logging for different applications. Meaning, I want for some applications that they log in a seperate loggingfile then the main server.log.
Thank you very much for sharing your experience.
tkrug0210's code listing has points to the answer. If you read through this
http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration you should find that:
Only the top level deployment may specify scoping. If you have an ear, containing other modules, only scoping specified in the ear META-INF/jboss-app.xml has any effect. This applies for any other deployment sitting in the deploy directory which contains other types of deployments. If a sar contains other deployments, only the sar META-INF/jboss-service.xml scoping has any effect.
This works for me BUT i have to remove common-logging.jar from my ear. Does anyone know of a way to get around custom tailoring the list of jars in an ear just to satisfy the JBoss CL?