logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Smith <psm...@aconex.com>
Subject Re: Naming log4j threads
Date Wed, 12 Dec 2007 05:54:51 GMT
cool, bug found.  Now, any consensus on naming patterns?  I'd plan to  
prefix all thread names with 'log4j-' and use a sensible suffice  
depending on the usage (make it aligned with the class name that  
launched it if that made logical sense).

Unless there's no objections I'll try that approach... ?

On 12/12/2007, at 4:11 PM, Jacob Kjome wrote:

> See:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41156
> Jake
> Paul Smith wrote:
>> I'm certain there's a bugzilla ticket for this, but even if there  
>> wasn't there should be, but we are the middle of cleaning up thread  
>> names in our app to easily identify their uses, and ran into the  
>> FileWatchdog.
>> Obviously a consistent pattern of thread names would be good across  
>> log4j threads.  Here's a straw-man for consideration:
>>  protected
>>  FileWatchdog(String filename) {
>>    super("log4j-FileWatchdog");
>> Thoughts?
>> Paul "I've been in a black hole for several weeks" Smith
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org

Paul Smith
Core Engineering Manager

The easy way to save time and money on your project

696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200  Fax: +61 3 9240 0299
Email: psmith@aconex.com  www.aconex.com

This email and any attachments are intended solely for the addressee.  
The contents may be privileged, confidential and/or subject to  
copyright or other applicable law. No confidentiality or privilege is  
lost by an erroneous transmission. If you have received this e-mail in  
error, please let us know by reply e-mail and delete or destroy this  
mail and all copies. If you are not the intended recipient of this  
message you must not disseminate, copy or take any action in reliance  
on it. The sender takes no responsibility for the effect of this  
message upon the recipient's computer system.

View raw message