I am by no means an authority on this subject. This is kind of a known problem with log4j and application containers. Or, rather, it's not really a problem because this is the expected behavior. Or so I've gathered.
>From what I've puzzled out the problem is all about Class loading. When you >instatiate a new Logger, it, by default uses the Hierarchy of the logger instantiated >above it. Or something close to that anway. The end result is that your >application's logging routines are forced into the same sandbox that JBoss's logging >routines are in, thus it uses JBoss's appenders, etc.. This cycle can be broken, but bugger me if I've figured out how! You have to deploy your own copy of the log4j.jar file (I think?) with your application. You must then instatiate an instace of the Hierarchy from the context of your application, with a seperate configuration file! I do not yet have a fully working example, but I'm working hard on it. If anyone beats me to it, please post your work. Here is the related documentation that really gave me the heads up: Supporting the log4j RepositorySelector in Servlet Containers View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844038#3844038 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844038 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
