Hi Ceki,

Thanks for confirming that for me.
As it stands, I currently have two problems which are preventing me refactoring 
from a very old logging framework to log4j (something I'd very much like to do).
The first (and most major problem) is the inability to release dynamic logging 
resources (as described by my previous post).
NDC's really don't help me here: I really do need to associate appenders with 
dynamic domains.
Im happy to hack the source code if necessary for my own custom use - but any 
pointers would be very useful. 
As it stands, I currently do ** not ** have to worry about clients using a 
logger which has been closed (so this might simplify things for me a bit).
Im wondering whether a custom logger / logger factory would be the right 
approach? 
Any pointers would be great - (for example, locking policy etc).

The second problem is the threading model for appenders doesn't currently seem 
all that scalable (Each AsyncAppender uses a single dedicated thread). When 
there are a large number of appenders each at various levels in the logging 
hierarchy, a configurable pool of threads may be a more scalable solution. 
Adding such support locally seems fairly trivial - but would this be a useful 
addition to the Log4J codebase? I'd be happy to add it if so.

The first problem mentioned is certainly my main priority at the moment though 
- so any insight would be greatly received.

Many thanks,

Dave

-----Original Message-----
From: Ceki G�lc� [mailto:[EMAIL PROTECTED] 
Sent: 21 April 2005 10:28
To: Log4J Users List
Subject: RE: Dynamic Loggers


Hello Dave,

As you observed, loggers cannot be removed. It is a well known limitation in 
the log4j design.

At 16:27 4/20/2005, you wrote:
>
> > Everything in Log4j can be accessed programatically.
>
>Thanks,
>
>So, if the Log4J API allows it, could someone please point me towards 
>the correct way to ** remove ** a logger? I certainly cant see it in 
>the documentation.
>
>Thanks,
>
>Dave

--
Ceki G�lc�

   The complete log4j manual: http://www.qos.ch/log4j/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to