sdeboy | 2 Jul 07:49 2004
Picon

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/help release-notes.html

sdeboy      2004/07/01 22:49:27

  Modified:    src/java/org/apache/log4j/chainsaw LogPanel.java
                        LoggerNameTreePanel.java
               src/java/org/apache/log4j/chainsaw/color RuleColorizer.java
               src/java/org/apache/log4j/chainsaw/help release-notes.html
  Log:
  Added automatic colorizing of selected node and child nodes in logger tree panel.  Deactivated when 'focus
on' is in use or the 'Root Logger' is selected.

  Revision  Changes    Path
  1.80      +1 -0      logging-log4j/src/java/org/apache/log4j/chainsaw/LogPanel.java

  Index: LogPanel.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/chainsaw/LogPanel.java,v
  retrieving revision 1.79
  retrieving revision 1.80
  diff -u -r1.79 -r1.80
  --- LogPanel.java	25 Jun 2004 06:25:06 -0000	1.79
  +++ LogPanel.java	2 Jul 2004 05:49:27 -0000	1.80
   <at>  <at>  -634,6 +634,7  <at>  <at> 
        * it's rule state changes.
        */
       ruleMediator.setLoggerRule(logTreePanel);
  +    colorizer.setLoggerRule(logTreePanel.getLoggerColorRule());

       /*
        * Color rule frame and panel

(Continue reading)

sdeboy | 2 Jul 19:14 2004
Picon

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw ChainsawAppenderHandler.java

sdeboy      2004/07/02 10:14:38

  Modified:    src/java/org/apache/log4j/spi LoggingEventFieldResolver.java
               src/java/org/apache/log4j/chainsaw
                        ChainsawAppenderHandler.java
  Log:
  Now using host from remoteSourceInfo (if available) as the 'hostname' property for use in Chainsaw if no
'hostname' property was provided on the event.

  Revision  Changes    Path
  1.8       +6 -1      logging-log4j/src/java/org/apache/log4j/spi/LoggingEventFieldResolver.java

  Index: LoggingEventFieldResolver.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/spi/LoggingEventFieldResolver.java,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- LoggingEventFieldResolver.java	10 May 2004 09:10:40 -0000	1.7
  +++ LoggingEventFieldResolver.java	2 Jul 2004 17:14:38 -0000	1.8
   <at>  <at>  -98,16 +98,21  <at>  <at> 
     	  }
         StringTokenizer tokenizer = new StringTokenizer(replaceText);
         StringBuffer result = new StringBuffer();
  +      boolean found = false;

         while (tokenizer.hasMoreTokens()) {
             String token = tokenizer.nextToken();
             if (isField(token) || token.toUpperCase().startsWith(PROP_FIELD)) {
                 result.append(getValue(token, event).toString());
(Continue reading)

hoju | 2 Jul 23:29 2004
Picon

cvs commit: logging-log4j-sandbox build.xml

hoju        2004/07/02 14:29:37

  Modified:    .        build.xml
  Log:
  update version to match the latest tag

  Jake

  Revision  Changes    Path
  1.15      +1 -1      logging-log4j-sandbox/build.xml

  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j-sandbox/build.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- build.xml	27 Apr 2004 12:51:02 -0000	1.14
  +++ build.xml	2 Jul 2004 21:29:37 -0000	1.15
   <at>  <at>  -16,7 +16,7  <at>  <at> 
     <property file="build.properties"/>
     <property file="build.properties.sample"/>

  -  <property name="version" value="0.2alpha"/>
  +  <property name="version" value="0.3alpha"/>

     <!-- The base directory relative to which most targets are built -->
     <property name="base" value="."/>
hoju | 2 Jul 23:32 2004
Picon

cvs commit: logging-log4j-sandbox/src/java/org/apache/log4j/servlet ServletContextLogAppender.java

hoju        2004/07/02 14:32:47

  Modified:    src/java/org/apache/log4j/servlet
                        ServletContextLogAppender.java
  Log:
  Added capability to log Throwable information if available.  Suggested by Stefan Armbruster.

  Jake

  Revision  Changes    Path
  1.3       +8 -1      logging-log4j-sandbox/src/java/org/apache/log4j/servlet/ServletContextLogAppender.java

  Index: ServletContextLogAppender.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j-sandbox/src/java/org/apache/log4j/servlet/ServletContextLogAppender.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ServletContextLogAppender.java	28 Feb 2004 13:55:05 -0000	1.2
  +++ ServletContextLogAppender.java	2 Jul 2004 21:32:47 -0000	1.3
   <at>  <at>  -18,6 +18,7  <at>  <at> 

   import org.apache.log4j.AppenderSkeleton;
   import org.apache.log4j.spi.LoggingEvent;
  +import org.apache.log4j.spi.ThrowableInformation;

   import java.util.Collections;
   import java.util.HashMap;
   <at>  <at>  -120,7 +121,13  <at>  <at> 
       }
(Continue reading)

noreply | 3 Jul 01:07 2004
Picon

[GUMP <at> brutus]: logging-log4j/log4j-tests failed

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 folk at general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration, and has been outstanding for 59 runs.
Project State : 'Failed', Reason 'Build Failed'

Full details are available at:

    http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/index.html

That said, some snippets follow:

The following annotations were provided:
 -INFO- Made directory [/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Enable "debug" output, due to a sequence of 58 previous errors.
 -INFO- Failed with reason build failed

The following work was performed:
http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/gump_work/build_logging-log4j_log4j-tests.html
Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 4 seconds
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
org.apache.tools.ant.Main -debug -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
(Continue reading)

bugzilla | 4 Jul 16:17 2004
Picon

Bug report for Log4j [2004/07/04]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|  569|Ver|Cri|2001-02-09|fully qualified class name used as category name c|
|  851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe|
|  900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W|
| 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th|
| 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer                |
| 7678|Opn|Nor|2002-04-02|if log file is deleted, data will be lost until de|
| 7948|Opn|Nor|2002-04-11|Layout & Subclasses: getFooter never called       |
| 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace   |
| 9150|New|Maj|2002-05-16|No check in FileAppender if parent-path exists    |
|10560|New|Nor|2002-07-08|DailyRollingAppender does not roll each period    |
|10587|New|Enh|2002-07-09|Illogical difference between removeAppender and re|
|11009|New|Min|2002-07-20|Cannot access XMLSample page                      |
|11142|New|Min|2002-07-24|org.apache.log4j.net.SocketServer doesn't work wit|
|11186|New|Min|2002-07-25|DefaultRenderer.doRender() does not handle NullPoi|
|11285|New|Nor|2002-07-30|SocketAppender fails to reconnect immediately     |
|11446|Ass|Nor|2002-08-03|Rolling, DailyRolling & FileAppender do not append|
|11474|New|Enh|2002-08-05|Improvements to rolling file appenders            |
(Continue reading)

Michael Karas | 5 Jul 17:14 2004
Picon

Context specific appenders for log4j

Hi log4j-dev-list !

We have developed 2 useful appenders for log4j which can be used for 
a file-logging on a context specific basis.

The context-key has to be set via MDC for each Thread.
The name of the key can be set as a parameter..(see log4j.xml below)

Therefore instead of having only one Logfile with pattern Like [Context: %8X{CONTEXT}] 
it is now possible to have separate Logfiles on a context-specific basis.
Additional any Logging with an empty MDC-Context-Key goes into a default Logfile.

The RollingContextFileAppender uses RollingFileAppenders internal, the
DailyRollingContextFileAppenders uses
- guess what - DailyRollingFileAppenders internal....

example log4j.xml configuration:
.....
  <appender name="Context_Appender" class="org.apache.log4j.RollingContextFileAppender"> 
    <param name="ContextKey" value="MYCONTEXT"/>	    <!-- Context key to be used (has to be set via MDC) -->
    <param name="FileName" value="c:/BSP_log"/>            <!-- Path and Filename -->
    <param name="MaxDefaultFileSize" value="5MB"/>        <!-- Maximum size of the default log (optional) -->
    <param name="MaxDefaultBackupIndex" value="3"/>    <!-- Maximum backup index of the default log
(optional) -->  
    <param name="MaxContextFileSize" value="1MB"/>       <!-- Maximum lofsize PER CONTEXT (optional) -->
    <param name="MaxContextBackupIndex" value="3"/>    <!-- Maximum backup index of EACH CONTEXT (optional)
-->     <layout class="org.apache.log4j.PatternLayout">
    	<param name="ConversionPattern" value="[%d{ISO8601}] %5p - %-18c : %m%n"/>
    </layout>
  </appender> 
(Continue reading)

noreply | 6 Jul 01:23 2004
Picon

[GUMP <at> brutus]: logging-log4j/log4j-tests failed

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 folk at general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration, and has been outstanding for 67 runs.
Project State : 'Failed', Reason 'Build Failed'

Full details are available at:

    http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/index.html

That said, some snippets follow:

The following annotations were provided:
 -INFO- Made directory [/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Enable "debug" output, due to a sequence of 66 previous errors.
 -INFO- Failed with reason build failed

The following work was performed:
http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/gump_work/build_logging-log4j_log4j-tests.html
Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 4 seconds
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
org.apache.tools.ant.Main -debug -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
(Continue reading)

Onyi | 6 Jul 17:33 2004
Picon

NTEventLogAppender.dll -Custom Event ID and Category

Hello,
 
I noticed in a post on Wed, 12 May 2004 to this mailing list somebody mentioned they were working on a custon NTEventLogAppender that would allow for custom EventIDs and Category names to be logged to the Windows Event Log.  Any news on this effort?  I would be very interested in using such a dll as I need to do just that (send custom event ids and category names to windows event log).  Thanks.
 
-Donald
Jon Russell | 6 Jul 22:25 2004

RE: NTEventLogAppender.dll -Custom Event ID and Category

I have some code written at this point, but I haven't been very proactive in actually creating the diff to add it to the log4j codeline as of yet.
 
Things that I was planning on doing:
-remove jdk 1.4 dependency (1 1.4 method is used)
-add more javadoc
-change existing file (the first version was done using a separate class to avoid log4j conflicts as it isn't a part of log4j yet)
 
Jon
-----Original Message-----
From: Onyi [mailto:cdonyi <at> yahoo.com]
Sent: Tuesday, July 06, 2004 8:34 AM
To: log4j-dev <at> jakarta.apache.org
Subject: NTEventLogAppender.dll -Custom Event ID and Category

Hello,
 
I noticed in a post on Wed, 12 May 2004 to this mailing list somebody mentioned they were working on a custon NTEventLogAppender that would allow for custom EventIDs and Category names to be logged to the Windows Event Log.  Any news on this effort?  I would be very interested in using such a dll as I need to do just that (send custom event ids and category names to windows event log).  Thanks.
 
-Donald

Gmane