headers
Alan Brown | 1 Apr 2004 02:10

RE: Static log reading tool...

My problem was localized enough that I was able to write a tool to do it
in an hour.  I plan to make it a bit more generic though when I return
from my vacation and I'll be happy to look at integrating my desired
functionality in chainsaw if you'd like.

alan

-----Original Message-----
From: Paul Smith [mailto:paul.smith <at> lawlex.com.au] 
Sent: Tuesday, March 30, 2004 3:05 PM
To: Log4J Users List
Cc: log4j-dev <at> logging.apache.org
Subject: RE: Static log reading tool...

On Wed, 2004-03-31 at 08:51, Alan Brown wrote:
> Can Chainsaw go to remote locations (specified as virtual drives so I
> guess that won't be a problemm) and read the file I specify into
> chainsaw, filtering out the parts that don't meet it's criteria.
> 

You can open a remote XMLLayout formatted file by using a URL (e.g
file://mnt/mydrive/.... or http://myserver/logs/log.xml) by using the
menu item under the File menu.

Once you have read in the file, a tab is created based an a unique name
(configured from the app preferences).  Chainsaw v2 will remember as
preferences the logger filters you use in the Log Tree panel on the
left, but I am not sure we've got around to storing remembered filter
expressions yet.  But you could paste in the filter expression you
created previously I guess until we get around to it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
ceki | 1 Apr 2004 08:54
Picon
Favicon

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

To whom it may engage...

This is an automated request, but not an unsolicited one. For help 
understanding the request please visit 
http://gump.apache.org/nagged.html, 
and/or contact general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration. The current state is 'Failed', for
reason 'Build Failed'

Full details are available at:
http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.html, however some snippets follow:

-  -  -  -  - -- -- ------------------------------------ G U M P

Gump provided these annotations:

 - Info - Made directory [/data3/gump/logging-log4j/tests/classes]
 - Info - Enable "verbose" output, due to 1 previous error(s).
 - Info - Failed with reason build failed
 - Info - Enable "debug" output, due to build failure.

-  -  -  -  - -- -- ------------------------------------ G U M P
Gump performed this work:

Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 1 minutes, 14 seconds
Command Line: java
-Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Collins | 2 Apr 2004 00:05
Picon
Favicon

log4j RSS Appender

Has anyone implemented this?

I wanted to ask before implementing my own.

I expect the RSS feed to be similar to the
current SMTP Appender. I expect infrequent
ERROR and INFO log entries.

I am thinking of making a jsp which uses
Informa ( http://informa.sourceforge.net )
to construct the feed from queries of the
table filled by a JDBC Appender.

Or maybe there is a better way?

Thanks!

=====
Andrew Collins - andrewrcollins <at> yahoo.com
http://profiles.yahoo.com/andrewrcollins/
Permalink | Reply | 0 comments |
headers
bugzilla | 2 Apr 2004 00:46
Picon
Favicon

DO NOT REPLY [Bug 27438] - JDBCAppender doesn't release connection in case of failure

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27438>.
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=27438

JDBCAppender doesn't release connection in case of failure

------- Additional Comments From clement.ong <at> shinetech.com  2004-04-01 22:46 -------
Hi Gino,

You're right that the JDBCAppender is not of production quality. This is the 
second problem I discovered in this class. The first was when we were using an 
old version of log4j which has the persistent major memory leak in the flush 
method and the most recent memory leak due to stale connection. This parcular 
problem is very subtle(which could be caused the firewall or a *database 
restart or crash.*) as it's very hard to pinpoint where the memory leak is 
occuring in.

In a J2EE environment it is ill advised to use file based logging destination 
as it contravene the EJB specification rule.  This is where JDBCAppender or 
JMSType destination could be use.
Permalink | Reply | 0 comments |
headers
bugzilla | 2 Apr 2004 00:46
Picon
Favicon

DO NOT REPLY [Bug 27505] - JDBCAppender: allow to use JNDI datasource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27505>.
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=27505

JDBCAppender: allow to use JNDI datasource

------- Additional Comments From clement.ong <at> shinetech.com  2004-04-01 22:46 -------
Hi Gino,

You're right that the JDBCAppender is not of production quality. This is the 
second problem I discovered in this class. The first was when we were using an 
old version of log4j which has the persistent major memory leak in the flush 
method and the most recent memory leak due to stale connection. This parcular 
problem is very subtle(which could be caused the firewall or a *database 
restart or crash.*) as it's very hard to pinpoint where the memory leak is 
occuring in.

In a J2EE environment it is ill advised to use file based logging destination 
as it contravene the EJB specification rule.  This is where JDBCAppender or 
JMSType destination could be use.
Permalink | Reply | 0 comments |
headers
bugzilla | 2 Apr 2004 00:48
Picon
Favicon

DO NOT REPLY [Bug 27505] - JDBCAppender: allow to use JNDI datasource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27505>.
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=27505

JDBCAppender: allow to use JNDI datasource

------- Additional Comments From clement.ong <at> shinetech.com  2004-04-01 22:48 -------
disregard my posting, it went to the wrong thread.
Permalink | Reply | 0 comments |
headers
ceki | 2 Apr 2004 07:43
Picon
Favicon

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

To whom it may engage...

This is an automated request, but not an unsolicited one. For help 
understanding the request please visit 
http://gump.apache.org/nagged.html, 
and/or contact general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration, and has been outstanding for 2
runs. The current state is 'Failed', for reason 'Build Failed'

Full details are available at:
http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.html, however some snippets follow:

-  -  -  -  - -- -- ------------------------------------ G U M P

Gump provided these annotations:

 - Info - Made directory [/data3/gump/logging-log4j/tests/classes]
 - Info - Enable "verbose" output, due to 1 previous error(s).
 - Info - Failed with reason build failed
 - Info - Enable "debug" output, due to build failure.

-  -  -  -  - -- -- ------------------------------------ G U M P
Gump performed this work:

Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 1 minutes, 14 seconds
Command Line: java
-Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar
(Continue reading)

Permalink | Reply | 0 comments |
headers
ceki | 3 Apr 2004 09:00
Picon
Favicon

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

To whom it may engage...

This is an automated request, but not an unsolicited one. For help 
understanding the request please visit 
http://gump.apache.org/nagged.html, 
and/or contact general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration, and has been outstanding for 3
runs. The current state is 'Failed', for reason 'Build Failed'

Full details are available at:
http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.html, however some snippets follow:

-  -  -  -  - -- -- ------------------------------------ G U M P

Gump provided these annotations:

 - Info - Made directory [/data3/gump/logging-log4j/tests/classes]
 - Info - Enable "verbose" output, due to 2 previous error(s).
 - Info - Failed with reason build failed
 - Info - Enable "debug" output, due to build failure.

-  -  -  -  - -- -- ------------------------------------ G U M P
Gump performed this work:

http://lsd.student.utwente.nl/gump/logging-log4j/gump_work/build_logging-log4j_log4j-tests.html
Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 3 minutes, 48 seconds
Command Line: java
(Continue reading)

Permalink | Reply | 0 comments |
headers
sdeboy | 3 Apr 2004 09:35
Picon
Favicon

cvs commit: logging-log4j/src/java/org/apache/log4j/rule LevelInequalityRule.java LikeRule.java

sdeboy      2004/04/02 23:35:53

  Modified:    src/java/org/apache/log4j/rule LevelInequalityRule.java
                        LikeRule.java
  Log:
  LikeRule and LevelInequalityRule serialization now supported - previously failed due to
non-serializable Level and ORO references

  Revision  Changes    Path
  1.5       +47 -8     logging-log4j/src/java/org/apache/log4j/rule/LevelInequalityRule.java

  Index: LevelInequalityRule.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/rule/LevelInequalityRule.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- LevelInequalityRule.java	27 Feb 2004 16:47:34 -0000	1.4
  +++ LevelInequalityRule.java	3 Apr 2004 07:35:53 -0000	1.5
   <at>  <at>  -16,26 +16,29  <at>  <at> 

   package org.apache.log4j.rule;

  +import java.io.IOException;
  +import java.util.Iterator;
  +import java.util.LinkedList;
  +import java.util.List;
  +
   import org.apache.log4j.Level;
   import org.apache.log4j.UtilLoggingLevel;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simon Kitching | 3 Apr 2004 10:13
Picon

Re: Patch proposal: SMTP appender post-trigger filtering by NDC

On Fri, 2004-03-26 at 15:55, Simon Kitching wrote:
> Hi All,
> 
> I've just completed a patch for SMTPAppender which uses NDC to filter
> the messages in the generated email so that only buffered messages which
> are "related" to the triggering event are included in the email. 
> 
> The app I need this feature for processes multiple message types
> concurrently in different threads, and if an error for message X occurs
> I want the resulting email to exclude debug/info/warn/etc messages about
> unrelated messages being processed at the same time, and about messages
> previously processed by the same thread which were not followed by a
> triggering event. By using a modified SMTPAppender, and setting the NDC
> to the "message id" when starting processing of a specific message, I
> get the desired effect.
> 
> Note that this is not the same as filtering, which decides which
> messages go into the buffer. [Potentially, this could be implemented by
> invoking a "post-trigger" filter object rather than hard-coding the
> behaviour into the appender as shown below].
> 
> Is there any interest in including this feature in log4j?

I didn't get any replies from the original posting. I hope no-one minds
this repost; I just want to make sure it didn't just get missed.

I understand that there would be a reasonable amount of work to knock
the code in my original posting into shape. If people here are
interested in the patch, I am willing to do so.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane