AW: modifying log levels through a management console

Hi Aaron, 'I built into my logger the ability to get a list of all logs ( categories ) and modify the log level of each during runtime, so I can turn on debugging and debug in a production environment if necessary, without restarting the servers and changing a config file. ' How it is possible?

Re: modifying log levels through a management console

Hi, We had a similar requirement of runtime modification of log levels in our project. We could do it easily since we had already instrumented our software using Applixray's AIC implementation for Java. However, it really boils down to just having a file modification listener that monitors the c

RE: modifying log levels through a management console

Title: RE: modifying log levels through a management console Hi there, I made such a console myself, and after even extending it a little bit more, I was planning to mail it Ceki as a contribution.  But if you really want to use it now, no problem, just mail me and I'll send it to you... Th

FW: JDBCAppender...

I have the following error when running the sample code below: log4j:ERROR No appenders could be found for category (com.mellon.te.logging.test.LogThisTester). log4j:ERROR Please initialize the log4j system properly. Any help with getting a sample JDBCAppender class writing messages to a DB woul

RE: JDBCAppender...

I spy this line in your config. file // Set the priority which messages have to be logged MyCat.setPriority(Priority.INFO); Since you're using MyCat.debug("foo") and the priority is set to INFO, I don't think there will be any output to any appender. Anyone else see different? T

Re: FW: JDBCAppender...

Hi, Run your application with the log4j.debug flag. As in java -Dlog4j.debug LogThisTester See comments below. At 11:09 05.06.2001 -0400, you wrote: >I have the following error when running the sample code below: > >log4j:ERROR No appenders could be found for category >(com.mellon.te.logging.

RE: modifying log levels through a management console

You don't need to jump through this many hoops to get this behavior - there is an easier way to achieve dynamic, run-time re-configuration using standard config files. Specifically, you don't need to roll your own file listener - Log4J already has one. To do this, you subclass FileWatchdog and t

RE: How to set additivity with xml config files

Mike, Change what you sent as an example to look like this: This is one of those things that's buried in the DTD. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

JDBCAppender update

I spent a lot of time yesterday updating my JDBCAppender. Looks like that was appropriate timing. The new version of my appender has bean-like get/set methods (plus the now deprecated setOption methods). Setting a database driver is a new option. Most valuably though I've made the sql setting mu

RE: Config docs or a User's Guide (Was: Help on property file settings for Appenders and Layouts)

Paul, >> That makes you the perfect person to start writing one. << ;-) Maybe not "perfect", but adequate, anyway! Ceki's current "User's Guide" *is* a good introduction, but I suspect it best serves the "advanced" end of the user/developer spectrum of the Log4J community. This is, obviously,

Re: modifying log levels through a management console

Were can I find a reference of the possible properties of an appender, for example the DailyRollingFileAppender ? Why ? I like to know how to filter log messages by his category when send to an appender. For example: the console should log message with category => DEBUG and the DailyRollingFileAp

RE: modifying log levels through a management console

>>Were can I find a reference of the possible properties of an appender, for example the DailyRollingFileAppender ? << There isn't one, yet. I've just started writing one, but it won't be done until the end of July, or mid-August. That's the short answer: the long answer == in fact, you can fi

RE: JDBCAppender update

Thanks Kevin! This worked out perfect, I was able to write to database without a problem... -Original Message- From: Kevin [mailto:[EMAIL PROTECTED]] Sent: Friday, June 05, 2020 12:13 PM To: [EMAIL PROTECTED] Subject: JDBCAppender update I spent a lot of time yesterday updating my JDBC

Re: modifying log levels through a management console

Mark Masterson wrote: > In your example, the easiest way to achieve what you're after is to use the > "Threshold" parameter, common to all Appenders, and set its priority as > appropriate. Is it more performant to set the log level via the Appender or via Categories? Here's my example... lo

RE: modifying log levels through a management console

>>Is it more performant to set the log level via the Appender or via Categories?<< Ah, here I'm likely to get myself in trouble, as this is (for me, at least) a subtle and complicated issue. Short answer: I think that you would find that setting the priority at the Category level is faster, in t

Simple Config file question

Hi all, I have a question about starting(read configuring) log4j. I am trying to use log4j with Weblogic and am using the Dlog4j.configuration=file:myfile#PropertyConfigurator option when starting-up WebLogic. I want to know how to set it up with the configureAndWatch option when starting up W

Re: modifying log levels through a management console

Mark Masterson wrote: > Short answer: I think that you would find that setting the priority at the > Category level is faster, in terms of absolute performance. That's what I was assuming for the reasons you mentioned in your explanation. As for benchmarking.. maybe after I get the product

Re: modifying log levels through a management console

At 10:52 05.06.2001 -0700, you wrote: >Mark Masterson wrote: > >>In your example, the easiest way to achieve what you're after is to use the >>"Threshold" parameter, common to all Appenders, and set its priority as >>appropriate. > > >Is it more performant to set the log level via the Appender o

Re: Simple Config file question

At 13:23 05.06.2001 -0500, you wrote: >Hi all, > >I have a question about starting(read configuring) log4j. I am trying to use >log4j with Weblogic and am using the > >Dlog4j.configuration=file:myfile#PropertyConfigurator > >option when starting-up WebLogic. I want to know how to set it >up with

Re: Exception after calling shutddown

I happens on Solaris also. Java 1.2.2_05a SunOS 5.8 Ross --- Ross Cormier <[EMAIL PROTECTED]> wrote: > Sorry for the lack of information. I am running on > NT > SP 5/Java 1.3.02. The exception is thrown without > fail. > > I will be able to test it on Solaris tomorrow. > > Thanks, > Ross

Re: Exception after calling shutddown

Ross, Which version of log4j is this? Ceki At 13:08 05.06.2001 -0700, you wrote: >I happens on Solaris also. > >Java 1.2.2_05a >SunOS 5.8 > >Ross > >--- Ross Cormier <[EMAIL PROTECTED]> wrote: >> Sorry for the lack of information. I am running on >> NT >> SP 5/Java 1.3.02. The exception is t

Re: Exception after calling shutddown

Ross, I tried the following config file with org.apache.log4j.test.Shallow with no problems. Can you try it as well? Ceki

FileWatchdog and multiple threads

I am using log4J in a J2EE environment and would like to reload the log4j configuration if the config file changes. I know I can use FileWatchdog and doOnChange(). But I am wondering whether this is safe? Between calling resetConfiguration() and doConfigure() is there any guarantee that some other

Re: FileWatchdog and multiple threads

Nope. Log4j is thread safe. Ceki At 16:56 05.06.2001 -0500, you wrote: >I am using log4J in a J2EE environment and would like to reload the log4j >configuration if the config file changes. I know I can use FileWatchdog and >doOnChange(). But I am wondering whether this is safe? Between calling >