Re: About NDC/MDC and threads

2006-02-20 Thread Endre Stølsvik
On Thu, 16 Feb 2006, Raul Carazo wrote: | Maybe there is an answer to my question but... If so, | please, refer me to it. | | Both NDC and MDC works on a thread, so if you create | another logger in another thread, you'll noy see the | value you had set before... | | Some servers, like Weblogic,

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-tests has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-tests has an issue affecting its community integration. This issue

Re: [logging] JCL2.0 design - Architecture

2006-02-20 Thread Boris Unckel
Hello, I know crossposting is not not wanted usually, but the case legitimates. The original thread on commons-dev discusses design of JCL2.0 for archticture and API, there were already some discussions about log4j 2.0 (i.E. http://marc.theaimsgroup.com/?l=log4j-dev&m=113625138015434&w=2). M

DO NOT REPLY [Bug 38717] New: - Application wide config chainsaw.xml overwritten when Tab Identifier = PROP.hostname

2006-02-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-chainsaw has an issue affecting its community integration. This iss

[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-chainsaw has an issue affecting its community integration. This iss

DO NOT REPLY [Bug 38717] - Application wide config chainsaw.xml overwritten when Tab Identifier = PROP.hostname

2006-02-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

svn commit: r379148 - in /logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw: ApplicationPreferenceModelSaver.java help/release-notes.html version/VersionManager.java

2006-02-20 Thread sdeboy
Author: sdeboy Date: Mon Feb 20 07:27:05 2006 New Revision: 379148 URL: http://svn.apache.org/viewcvs?rev=379148&view=rev Log: Changing global settings file from chainsaw.xml to chainsaw.settings.xml to address bugzilla issue 38717. Current users will have to re-apply their global settings (con

DO NOT REPLY [Bug 38717] - Application wide config chainsaw.xml overwritten when Tab Identifier = PROP.hostname

2006-02-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-tests has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

2006-02-20 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j-tests has an issue affecting its community integration. This issue