Re: Level per user

2006-10-17 Thread Jacob Kjome
At 08:11 AM 10/17/2006, you wrote: >Hi Jacob and all, >I searched in the archives for the reason to wrapper the log and not >just extend it. I found two reason: >1. FQCN: the FQCN is defined in the Logger class so I could have some >problems in the stacktrace handling when i want log also the sour

Re: Level per user

2006-10-17 Thread Michael Giroux
Stefano, On 10/17/06, Stefano Nichele <[EMAIL PROTECTED]> wrote: and I should log any message in both loggers and i should redirect to the myDebugLogger the log coming from some user...ehmmmi'm confusedcan you give me more details ? messages logged to x.y.z.debug will be sent automati

Re: Dynamic reconfiguration

2006-10-17 Thread David Tonhofer
David Grigglestone wrote: From what I remember to dynamically reconfigure log4j with 1.2 you need to have log4j loaded in a separate class loader and create a new class loader to configure with a different configuartion file .. please confirm this is the case. Also will this change in 1.3? ..

Re: Level per user

2006-10-17 Thread Stefano Nichele
Hi Michael, I read some threads about that and the user level, but I don't like this way. What I understood (i think no :-) ) about the use of multiple loggers is that I should have in my classes always availble more than one logger: Logger myLogger = new Logger("x.y.z"); Logger myDebugLogg

Dynamic reconfiguration

2006-10-17 Thread David Grigglestone
From what I remember to dynamically reconfigure log4j with 1.2 you need to have log4j loaded in a separate class loader and create a new class loader to configure with a different configuartion file .. please confirm this is the case. Also will this change in 1.3? .. the javadoc for 1.3 is not

Re: Multiple threads that log events to the same file concurrently

2006-10-17 Thread Curt Arnold
log4j can evaluate many threshold checks (that is, is the level high enough that this should be logged) concurrently, but its current design can only process one logging request at a time once it passes the threshold test. Eliminating that aspect of the design is the major design goal for

Re: Level per user

2006-10-17 Thread Michael Giroux
Have you considered using multiple loggers? You could configure a standard logger with WARN or ERROR level: log4j.logger.com.myco.myapp=WARN,a1 You could configure additional loggers that would be used when you want individual users to be logging at lower levels: log4j.logger.com.myco.myapp.de

Re: Level per user

2006-10-17 Thread Stefano Nichele
Hi Jacob and all, I searched in the archives for the reason to wrapper the log and not just extend it. I found two reason: 1. FQCN: the FQCN is defined in the Logger class so I could have some problems in the stacktrace handling when i want log also the source class/method of the call. I read t

Re: Multiple threads that log events to the same file concurrently

2006-10-17 Thread James Stauffer
You could try writing logs to a database, JMS, or a Socket. On 10/17/06, Cohen Oren (ICS) <[EMAIL PROTECTED]> wrote: Hi Short description of the problem: "I need the best log4j configuration for - Multiple threads that log events to the same file concurrently" I work on a multithreaded environ

Multiple threads that log events to the same file concurrently

2006-10-17 Thread Cohen Oren \(ICS\)
Hi Short description of the problem: "I need the best log4j configuration for - Multiple threads that log events to the same file concurrently" I work on a multithreaded environment (between 10-20 threads). I want all the threads to log their events to the same log file. Currently, there are 3 Lo