First, define logging for the root logger. I usually set this to some relatively high level, such as WARN, so that extraneous logging performed by any given library logging debug or info statements is squashed. However, I still want to see problems when they appear. WARN fits the bill.
Next, if you want more logging from a particular hierarchy, define that and lower logging level as desired. Because you are only lowering the level for your defined hierarchy, you won't get extraneous logging from libraries other than those matching your hierarchy (conventionally named by package).
This is all very basic stuff. If you haven't yet read up on Log4j, please do so before posting questions here. We're happy to help, but you should understand the basics before posting. If you do understand the basics and have posed a more nuanced question than I have given it credit for, please accept my apologies and explain in more detail what you are driving at.
Jake On Wed, 2 Jan 2008 13:16:21 +0530 "Raghuveer" <[EMAIL PROTECTED]> wrote:
Hello, I was thinking to explore for both requirements. If it is not possible to stop creation of log file, then at least I want to implement stopping logging related to struts. So there will be only application related logs. -----Original Message-----From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Monday, December 31, 2007 4:35 AMTo: Log4J Users List Subject: Re: How to Stop logging I'm not clear on the goal here? Are you trying to avoid logging or avoidthe file creation in the first place? There is no way I know of to prevent the file from being created that is defined for the appender in the configuration. Preventing logging from going to that file is a totally separate issue. Pleaseclarify. Jake Raghuveer wrote:Instead of putting fatal and minimizing the logs .I tried as below from other replies for this subject which is also not WorkingThe way to stop logging is to set the threshold "OFF"log4j.logger.com.testapp.test=OFF_____ From: Sharma, Manu IN GGN SISL [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 11:41 AMTo: Log4J Users List; [EMAIL PROTECTED]Subject: RE: How to Stop loggingPossible workaround : log4j.logger.com.testapp.test=fatal, test Description : Write fatal instead of debug, it would only display logging for fatal level and rest other will be automatically stopped. This way you can minimized the amount of logging generated.-----Original Message-----From: Raghuveer [mailto:[EMAIL PROTECTED] Sent: Thursday, December 27, 2007 10:40 AMTo: [email protected]Subject: How to Stop loggingIs there way to stop logging in the application..This is my configuration of log4j.propertieslog4j.logger.com.testapp.test=debug, testlog4j.appender.test=org.apache.log4j.RollingFileAppenderlog4j.appender.test.File=\\\\logsserver\\APP_LOGS\\test\\test.loglog4j.appender.test.MaxFileSize=5000KBlog4j.appender.test.MaxBackupIndex=10log4j.appender.test.layout=org.apache.log4j.PatternLayout#log4j.appender.test.layout.ConversionPattern=%d~%p~%c~ %m%nImportant notice:This e-mail and any attachment thereto contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank You.--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
