date:20060220

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, uses several threads, so
| it's possible that you don't take the same thread in
| your  web Session.

Where do they use several threads? You are guaranteed that in the same 
method-invocation, e.g. doPost(), obviously just one thread will do the 
run.

If however you go outside that thread, by invoking some other resource, or 
using some worker-pool, you're obviously out of luck on that approach. I 
guess you'll basically have to send along some context-object that enable 
you to bind back to the original requestor.

| 
| I'd like to set a value (id of the person in session)
| for a HttpSession, not a thread. IS it possible???

I do something along the lines of this: I have a super-servlet that 
implements the service() method, fetches the httpsession, fetches the id, 
shoves it into the NDC, going into a try-finally block, doing 
super.service (or call some "specialService()" method instead), and in the 
finally block, i do NDC.remoce().

Note the -remove- call. It shouldn't have been necessary (.clear() should 
have been sufficient), but the NDC as it stands has implemented this in a 
very strange, inefficient and bad way: instead of using a ThreadLocal, 
they use "their own" synchronized-hitting threadlocal implementation. If 
you don't call remove, _your application_ will never be fully freed from 
the thread, and you can utterly forget reloading in e.g. tomcat. That 
added to the fact that this implementation is very costly compared to the 
real ThreadLocal: synching.

_However_, the new java threadlocal (from java 1.3) have another problem: 
it very often cause stale data in servlet containers that recycle their 
threads when reloading an application (as they all do), and you're back at 
the beginning. However, this is not as bad as forgetting to do .remove() 
on the current log4j impl, as that will -keep the thread object- around 
forever.

If you don't like psycho memory leaks; check out, and vote for, this bug:
  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6254531

Some background for that bug:
  http://www.jroller.com/page/tackline?entry=fixing_threadlocal

Basically: an object of a class from the webapp which is held in a 
threadlocal, will hold a reference to its class, which holds a reference 
to its classloader, which again holds a reference to all classes loaded by 
that loader, which means that all statics in all those classes will be 
"reachable gc-roots", which means that all objects they point to will be 
held. If such a static is a ThreadLocal (which is often the way 
threadlocals are used), you're screwed: the Thread will end up holding 
your entire web application inside one or several entries in its 
threadlocal map, and won't ever let go.

Regards
Endre.

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

[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 affects 1 projects,
 and has been outstanding for 4 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-tests :  Reliable, fast and flexible logging package for 
Java


Full details are available at:

http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet-api.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/gump_work/build_logging-log4j_logging-log4j-tests.html
Work Name: build_logging-log4j_logging-log4j-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 43 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dservlet-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
 regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/logging-log4j/tests/classes:/usr/local/gump/public/workspace/logging-log4j/tests/resources:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-smtp-20022006.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar
-
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,750 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:574)- Parsing for [root] 
with value=[DEBUG,A2].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,750 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:589)- Level token is 
[DEBUG].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,751 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:606)- Category root set to 
DEBUG.
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,751 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:623)- Parsing appender 
named "A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,752 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseAppender:676)- Parsing layout 
options for "A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,753 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[conversionPattern] to [%d{ABSOLUTE} %c [%p] - %m%n].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,753 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseAppender:684)- End of parsing for 
"A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,756 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[append] to [false].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,756 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[file] to [output/watchdog.FileWatchdog.test2.output.txt].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,757 DEBUG [main] 
org.apache.log4j.FileAppender#setFile:261)- setFile called: 
output/watchdog.FileWatchdog.test2.output.txt, false
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,757 DEBUG [main] 
org.apache.log4j.FileAppender#setFile:301)- setFile ended
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,758 DEBUG [main] 
org.apache.log4j.

[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 affects 1 projects,
 and has been outstanding for 4 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-tests :  Reliable, fast and flexible logging package for 
Java


Full details are available at:

http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet-api.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/gump_work/build_logging-log4j_logging-log4j-tests.html
Work Name: build_logging-log4j_logging-log4j-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 43 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dservlet-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
 regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/logging-log4j/tests/classes:/usr/local/gump/public/workspace/logging-log4j/tests/resources:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-smtp-20022006.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar
-
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,750 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:574)- Parsing for [root] 
with value=[DEBUG,A2].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,750 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:589)- Level token is 
[DEBUG].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,751 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:606)- Category root set to 
DEBUG.
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,751 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseCategory:623)- Parsing appender 
named "A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,752 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseAppender:676)- Parsing layout 
options for "A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,753 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[conversionPattern] to [%d{ABSOLUTE} %c [%p] - %m%n].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,753 DEBUG [main] 
org.apache.log4j.PropertyConfigurator#parseAppender:684)- End of parsing for 
"A2".
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,756 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[append] to [false].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,756 DEBUG [main] 
org.apache.log4j.config.PropertySetter#setProperty:222)- Setting property 
[file] to [output/watchdog.FileWatchdog.test2.output.txt].
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,757 DEBUG [main] 
org.apache.log4j.FileAppender#setFile:261)- setFile called: 
output/watchdog.FileWatchdog.test2.output.txt, false
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,757 DEBUG [main] 
org.apache.log4j.FileAppender#setFile:301)- setFile ended
[junit] LOG4J-INTERNAL: 2006-02-20 02:58:11,758 DEBUG [main] 
org.apache.log4j.

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).


Maybe this is a good point to talk again about the possibility to 
combine both APIs.
(Similiar discussion, but not completely matching: 
http://issues.apache.org/bugzilla/show_bug.cgi?id=34185)


log4j 2.0 could implement o.a.c.l.Log and JCL2.0 could detect this 
native implementation and

avoid the use of an wrapper class.

What do you think?

Regards
Boris

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

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_bug.cgi?id=38717

   Summary: Application wide config chainsaw.xml overwritten when
Tab Identifier = PROP.hostname
   Product: Log4j
   Version: 1.2
  Platform: All
OS/Version: All
Status: NEW
  Severity: minor
  Priority: P4
 Component: chainsaw
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: [EMAIL PROTECTED]


We use chainsaw to monitor various application across different servers, and to
help organise this visually we set the "Application-wide Preferences" -> "Tab
identifier" to "PROP.hostname". This allows us to arbitrarily group log messages
onto the same tab.

The problem here is that Chainsaw messages are then sent to a tab called
"Chainsaw", which then creates the config files "Chainsaw.colors",
"Chainsaw.properties" and "Chainsaw.xml". The last filename conflicts with the
application wide config file of the same name.

Depending on whether or not a user has applied layout changes to the "Chainsaw"
tab, and on which file is written to last when closing chainsaw, the application
wide file may or may not be overwritten with the Tab config file.

To remedy this, we've set the "Tab identifier" to "PROP.hostname -", but it's
kind of a messy solution. Would it not make more sense to name the global xml
config file to something more specific ie; chainsaw.settings.xml to match the
name of the properties file for instance?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

[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 issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-chainsaw :  Chainsaw log viewer


Full details are available at:

http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=20022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-chainsaw/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-20022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-20022006.jar:/usr/local/gump/public/workspace/xstream/xstream-20022006.jar:/usr/local/gump/public/workspace/jmdns/lib/jmdns.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.1/lib/jms.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar
-
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:618:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac]   new AppenderSkeleton() {
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:626:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac] public boolean requiresLayout() {
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:155:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac] URLEncoder.encode(p.getNamespace() + 
".properties"));
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:247:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac]  
URLEncoder.encode(profileable.getNamespace()) + ".properties")));
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogPanel.java:1190:
 warning: [deprecation] Date(java.lang.String) in java.util.Date has been 
deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac]  ^

[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 issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-chainsaw :  Chainsaw log viewer


Full details are available at:

http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=20022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-chainsaw/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-20022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-20022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-20022006.jar:/usr/local/gump/public/workspace/xstream/xstream-20022006.jar:/usr/local/gump/public/workspace/jmdns/lib/jmdns.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.1/lib/jms.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar
-
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:618:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac]   new AppenderSkeleton() {
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:626:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac] public boolean requiresLayout() {
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:155:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac] URLEncoder.encode(p.getNamespace() + 
".properties"));
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:247:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac]  
URLEncoder.encode(profileable.getNamespace()) + ".properties")));
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogPanel.java:1190:
 warning: [deprecation] Date(java.lang.String) in java.util.Date has been 
deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac]  ^

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_bug.cgi?id=38717


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |ASSIGNED




--- Additional Comments From [EMAIL PROTECTED]  2006-02-20 15:39 ---
I'll make the suggested change.

There is one drawback to this change which affects existing Chainsaw users -
their global settings won't be loaded (loaded config file, tab identifier, etc)
- they'll have to re-apply their changes.

They recently had to go through this when we started to use Xstream to load most
Chainsaw settings - and Chainsaw is still alpha (2 years now?), so not much harm
done, just a bit annoying.

I'll add a note in the release notes when I make the change.




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

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 (configuration url, tab identifier, etc.)

Modified:

logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/ApplicationPreferenceModelSaver.java

logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html

logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java

Modified: 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/ApplicationPreferenceModelSaver.java
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/ApplicationPreferenceModelSaver.java?rev=379148&r1=379147&r2=379148&view=diff
==
--- 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/ApplicationPreferenceModelSaver.java
 (original)
+++ 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/ApplicationPreferenceModelSaver.java
 Mon Feb 20 07:27:05 2006
@@ -19,7 +19,7 @@
  * 
  * The Model passed to this class' constructor is the instance of the 
ApplicationPreference
  * that will be saved, and will have properties modified by loading from the
- * 'chainsaw.xml' file in the .chainsaw directory of the user's home directory.
+ * 'chainsaw.settings.xml' file in the .chainsaw directory of the user's home 
directory.
  * 
  * @author psmith
  *
@@ -68,7 +68,7 @@
 }
 
 private File getApplicationPreferenceXMLFile(File settingsLocation) {
-return new File(settingsLocation, "chainsaw.xml");
+return new File(settingsLocation, "chainsaw.settings.xml");
 }
 
 }

Modified: 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html?rev=379148&r1=379147&r2=379148&view=diff
==
--- 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
 (original)
+++ 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
 Mon Feb 20 07:27:05 2006
@@ -5,9 +5,15 @@
 
 
 
-Release Notes
-
+Release Notes
+
+NOTE: The mechanism and format used to persist settings in Chainsaw is 
subject to change during this alpha phase.  If you are experiencing problems 
displaying events in Chainsaw, please delete everything in the 
$user.dir/.chainsaw directory.
+
 1.99.99
+20 February 2006
+
+Using a different file name to load and save global settings (from 
chainsaw.xml to chainsaw.settings.xml).  NOTE:Users will need to 
re-apply their application-wide settings or copy chainsaw.xml to 
chainsaw.settings.xml.
+
 09 February 2006
 
 Receiver help files were missing from the distribution. 
@@ -16,7 +22,6 @@
 
 Save/load of custom event columns now supported, as well as column 
order.
 
-NOTE: The mechanism and format used to persist settings in Chainsaw 
is changing significantly with this release, and is subject to change during 
this alpha phase.  If you are experiencing problems displaying events in 
Chainsaw, please delete everything in the $user.dir/.chainsaw directory.
 2 February 2006/h2>
 
 Revamped build system for easier maintenance and deployment of builds. 
Fixed issues with Commons VFS and Webstart.

Modified: 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java?rev=379148&r1=379147&r2=379148&view=diff
==
--- 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
 (original)
+++ 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
 Mon Feb 20 07:27:05 2006
@@ -10,7 +10,7 @@
 
 private static final VersionManager instance = new VersionManager();
 
-private static final String VERSION_INFO = "1.99.99 (09 February 2006)";
+private static final String VERSION_INFO = "1.99.99 (20 February 2006)";
 
 public static final VersionManager getInstance() {
 return instance;



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

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_bug.cgi?id=38717


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2006-02-20 16:29 ---
Committed - will show up in the Web Start build/bundle/Mac dmg image at some
point in the near future (after a few unrelated fixes/enhancements are made).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

[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 affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-tests :  Reliable, fast and flexible logging package for 
Java


Full details are available at:

http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet-api.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/gump_work/build_logging-log4j_logging-log4j-tests.html
Work Name: build_logging-log4j_logging-log4j-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 42 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dservlet-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
 regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/logging-log4j/tests/classes:/usr/local/gump/public/workspace/logging-log4j/tests/resources:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-smtp-20022006.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar
-
[junit] 2006-02-20 18:32:39,147 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--17
[junit] 2006-02-20 18:32:39,257 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--18
[junit] 2006-02-20 18:32:39,369 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--19
[junit] 2006-02-20 18:32:39,478 WARN 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--20
[junit] 2006-02-20 18:32:39,588 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--21
[junit] 2006-02-20 18:32:39,698 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--22
[junit] 2006-02-20 18:32:39,808 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--23
[junit] 2006-02-20 18:32:39,918 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--24
[junit] -  ---

[junit] Testcase: test1 took 3.211 sec
[junit] Testcase: test2 took 2.752 sec

Rolling:

NDC:
[junit] Running org.apache.log4j.NDCTestCase
[junit] Testsuite: org.apache.log4j.NDCTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.187 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.187 sec
[junit] - Standard Output ---
[junit] Tearing down test case.
[junit] -  ---

[junit] Testcase: test1 took 0.178 sec

Plugins:
[junit] Running org.apache.log4j.plugins.PluginTestCase
[junit] Testsuite: org.apache.log4j.plugins.PluginTestCase
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.004 sec
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.004 sec


FileWatchdog:
[junit] Running org.apache.log4j.watchdog.FileWatchdogTestCase
[junit] Testsuite: org.apache.log4j.watchdog.FileWatchdogTestCase
[junit] Tests run: 1, Failures: 1, Errors: 0, Time e

[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 affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-tests :  Reliable, fast and flexible logging package for 
Java


Full details are available at:

http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property 
servlet-api.jar.
 -INFO- Made directory 
[/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j/logging-log4j-tests/gump_work/build_logging-log4j_logging-log4j-tests.html
Work Name: build_logging-log4j_logging-log4j-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 42 secs
Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dservlet-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
 regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/logging-log4j/tests/classes:/usr/local/gump/public/workspace/logging-log4j/tests/resources:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-20022006.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-20022006.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-smtp-20022006.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar
-
[junit] 2006-02-20 18:32:39,147 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--17
[junit] 2006-02-20 18:32:39,257 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--18
[junit] 2006-02-20 18:32:39,369 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--19
[junit] 2006-02-20 18:32:39,478 WARN 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--20
[junit] 2006-02-20 18:32:39,588 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--21
[junit] 2006-02-20 18:32:39,698 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--22
[junit] 2006-02-20 18:32:39,808 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--23
[junit] 2006-02-20 18:32:39,918 DEBUG 
org.apache.log4j.rolling.FilterBasedRollingTest -Hello--24
[junit] -  ---

[junit] Testcase: test1 took 3.211 sec
[junit] Testcase: test2 took 2.752 sec

Rolling:

NDC:
[junit] Running org.apache.log4j.NDCTestCase
[junit] Testsuite: org.apache.log4j.NDCTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.187 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.187 sec
[junit] - Standard Output ---
[junit] Tearing down test case.
[junit] -  ---

[junit] Testcase: test1 took 0.178 sec

Plugins:
[junit] Running org.apache.log4j.plugins.PluginTestCase
[junit] Testsuite: org.apache.log4j.plugins.PluginTestCase
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.004 sec
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.004 sec


FileWatchdog:
[junit] Running org.apache.log4j.watchdog.FileWatchdogTestCase
[junit] Testsuite: org.apache.log4j.watchdog.FileWatchdogTestCase
[junit] Tests run: 1, Failures: 1, Errors: 0, Time e

Re: About NDC/MDC and threads

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

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

Re: [logging] JCL2.0 design - Architecture

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

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

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

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

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

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

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

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

12 matches

Site Navigation

Mail list logo

Footer information