You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Paul Smith <ps...@aconex.com> on 2007/12/11 06:58:48 UTC
Naming log4j threads
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
Re: Naming log4j threads
Posted by Paul Smith <ps...@aconex.com>.
On 12/12/2007, at 5:27 PM, Jacob Kjome wrote:
>
>
> Paul Smith wrote:
>> 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... ?
>
> I'm sorry, but, unfortunately, I have "no objections". I guess
> you'll have to come up with a different approach. Heh :-)
>
hehee. that wasn't phrased well was it?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Naming log4j threads
Posted by Jacob Kjome <ho...@visi.com>.
Paul Smith wrote:
> 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... ?
>
I'm sorry, but, unfortunately, I have "no objections". I guess you'll have to
come up with a different approach. Heh :-)
Jake
> Paul
> 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
>
> *Aconex*
> **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 <ma...@aconex.com> * www.aconex.com**
> <http://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.**
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Naming log4j threads
Posted by Paul Smith <ps...@aconex.com>.
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... ?
Paul
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
Aconex
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.
Re: Naming log4j threads
Posted by Jacob Kjome <ho...@visi.com>.
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