Return-Path: Delivered-To: apmail-jakarta-log4j-dev-archive@apache.org Received: (qmail 80202 invoked from network); 29 Jan 2002 22:10:41 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Jan 2002 22:10:41 -0000 Received: (qmail 5465 invoked by uid 97); 29 Jan 2002 22:10:45 -0000 Delivered-To: qmlist-jakarta-archive-log4j-dev@jakarta.apache.org Received: (qmail 5430 invoked by uid 97); 29 Jan 2002 22:10:45 -0000 Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@jakarta.apache.org Received: (qmail 5419 invoked from network); 29 Jan 2002 22:10:44 -0000 From: "Tom Innes" To: Subject: log4J / JBoss Date: Tue, 29 Jan 2002 17:11:59 -0500 Message-ID: <000201c1a911$f8df0c70$6901a8c0@TGIDesktopW20> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, I'm not sure if this is the correct place to ask this question, but if not, I apologize. Can anyone assist me in getting log4j to work properly with JBoss 2.4.3? We are extending the Category class with a our own. This works fine as a standalone java program. We are having problems, however, getting it to work with JBoss. The log4j.properties file looks like the following: ######################################################## # A log4j properties file suitable for replacing the # default JBoss ConsoleLogging & FileLogging mbeans. # Set the JBossCategoryFactory as the default CategoryFactory log4j.categoryFactory=org.jboss.logging.log4j.JBossCategory$JBossCategoryFac tory log4j.rootCategory=DEBUG, Default, Console ### The server.log file appender log4j.appender.Default=org.apache.log4j.FileAppender log4j.appender.Default.File=../log/server.log log4j.appender.Default.layout=org.apache.log4j.PatternLayout # Use the default JBoss format log4j.appender.Default.layout.ConversionPattern=[%c{1}] %m%n # Truncate if it aleady exists. log4j.appender.Default.Append=false #Example of turning off logging for a category. Uncomment to turn off. #log4j.category.DefaultDS=FATAL ### The console appender log4j.appender.Console=org.jboss.logging.log4j.ConsoleAppender log4j.appender.Console.Threshold=INFO log4j.appender.Console.layout=org.apache.log4j.PatternLayout log4j.appender.Console.layout.ConversionPattern=[%c{1}] %m%n # Example of only showing INFO msgs for any categories under org.jboss.util #log4j.category.org.jboss.util=INFO # An example of enabling the custom TRACE level priority that is used # by the JBoss internals to diagnose low level details. This example # turns on TRACE level msgs for the org.jboss.ejb.plugins package and its # subpackages. This will produce A LOT of logging output. #log4j.category.org.jboss.ejb.plugins=TRACE#org.jboss.logging.log4j.TracePri ority # EJBEnterprise Changes FOLLOW.......... # A log4j properties file suitable for replacing the # default JBoss ConsoleLogging & FileLogging mbeans. # Set the JBossCategoryFactory as the default CategoryFactory #log4j.rootCategory=DEBUG # Following lines have been added for EJBUserCategory # set up the category factory log4j.categoryFactory=com.ejbenterprise.util.logging.EJBUserCategoryFactory log4j.factory.ejbuser=Greg # set up the appender log4j.appender.EJBUserAppender=org.apache.log4j.FileAppender log4j.appender.EJBUserAppender.File=FilteredUser.log log4j.appender.EJBUserAppender.layout=com.ejbenterprise.util.logging.EJBUser PatternLayout log4j.appender.EJBUserAppender.layout.ConversionPattern=User: %u [%c{1}] %m%n log4j.appender.EJBUserAppender.Append=false # set up logging for a class log4j.category.com.ejbenterprise.util.server=DEBUG, EJBUserAppender ################################################## Now, when the server starts, we are getting ClassNotFoundException for core log4j classes like Category, Priority etc. Does anybody know why this happens and what the correct way to configure JBoss / log4j is? -Tom -- To unsubscribe, e-mail: For additional commands, e-mail: