Log4j development

noreply | 1 Oct 2006 14:00

[GUMP <at> vmgump]: Project logging-log4j-tests (in module logging-log4j) 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 the folk at general <at> gump.apache.org.

Project logging-log4j-tests has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 8 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: 3 mins 19 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

(Continue reading)

headers

bugzilla | 2 Oct 2006 08:08

Bug report for Log4j [2006/10/01]

+---------------------------------------------------------------------------+
| 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|
|11512|New|Nor|2002-08-06|Chainsaw forces output of its internal messages to|
|13099|New|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|14350|New|Enh|2002-11-07|Patch to substitute variables in the log4j.configu|
|15585|Ver|Maj|2002-12-20|log4j does not show Class Name, Method, or Line Nu|
|16280|New|Min|2003-01-21|Error Message always logged to log4j when calling |
|17498|New|Nor|2003-02-27|Logging inconsistencies using DailyRollingFileAppe|
|17511|Opn|Enh|2003-02-28|Patch for Chainsaw to utilise Receiver framework  |
|17531|New|Min|2003-02-28|PropertyConfigurator.configureAndWatch() don't res|
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|19902|New|Nor|2003-05-13|PropertyConfigurator throws ExceptionInInitializer|
|20395|New|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|21796|New|Nor|2003-07-22|SocketAppender doesn't fall back with FallbackErro|
|22894|Opn|Nor|2003-09-02|Single backslash not accepted in File param value |
|22934|Opn|Nor|2003-09-04|org.apache.log4j.jmx is not compatible with JMX 1.|
|23202|New|Enh|2003-09-16|l7dlog() methods do not support FQCN of wrapper cl|
|23329|New|Maj|2003-09-22|resourceBundle property within XML configuration f|

(Continue reading)

headers

noreply | 2 Oct 2006 12:07

[GUMP <at> vmgump]: Project logging-log4j-tests (in module logging-log4j) 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 the folk at general <at> gump.apache.org.

Project logging-log4j-tests has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 10 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: 3 mins 19 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

(Continue reading)

headers

Bender Heri | 2 Oct 2006 20:12

Enhanced FileAppender

Hello all

Since in user list nobody commented my suggestion for an enhancement of the FileAppender I will repeat it here.

Problem:
A often asked issue in user list is the problem to separate log files dependent on different criterias, like
a client-ID in a server environment, a mandant- or task-ID in scheduler applications, etc. Although it is
possible to achieve this with the existing log4j framework all possible solutions are quite complex or
have other drawbacks (own repository selector, working with different classloaders, subclass
concrete descendents of FileAppender).

Solution:
The FileAppender is supplied with a property of type FileNameBuilder (Design pattern: visitor). The
user-supplied implementation of this Interface can build a filename based on whatever criterias (i.e.
MDC, global Environment, etc.). The visitor is called each time a Fileappender wants to append a log
message. The FileAppender holds a collection of file writers for each separate file name delivered by FileNameBuilder.
To avoid the excess of open file handles the FileAppender could watch the logging activity to one
particular file. If the file was not accessed after let's say one hour it could be closed (this timeout
could also be configurable). Special care must be done if the property "append" of the FileAppender is
false. If the file was closed because the above timeout had elapsed and then reopened later again, the file
shouldn't be overridden.
If the config file does not specify a FileNameBuilder a default implementation would be used which returns
always the configured filename. This wouldn't break existing code. The existing property fileName
would remain and hold always the configured filename.

The interface of the FileNameBuilder would be like this:

public String buildFilename( FileAppender aFileAppender );

Any comments on this?

(Continue reading)

headers

bugzilla | 3 Oct 2006 09:54

DO NOT REPLY [Bug 40212] - NullPointerException in getLogger when called from ShutdownHook

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=40212>.
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=40212

------- Additional Comments From florian.kirchmeir <at> gmx.at  2006-10-03 00:54 -------
Hi all!
I can still confirm this bug using log4j-1.2.14.
Same stacktrace.

Regards,
Florian

--

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

headers

patrick | 3 Oct 2006 11:09

Re: Enhanced FileAppender

hi heri,

i like the idea a lot.
however (admittedly without thinking to much about it ;-} ) i'd use
"Strategy pattern" http://www.dofactory.com/Patterns/PatternStrategy.aspx

and something like:
FileNameBuilder {
 public String buildFilename( LoggingEvent event );
}

maybe it would be an idea to add a method
 public boolean closeFileAfter( LoggingEvent event );

to make it possible to close the files with a specific log event.

but that's just some quick toughts ;-}

best regards
patrick

Bender Heri wrote:
> 
> Hello all
> 
> Since in user list nobody commented my suggestion for an enhancement of
> the FileAppender I will repeat it here.
> 
> Problem:

(Continue reading)

headers

noreply | 3 Oct 2006 12:15

[GUMP <at> vmgump]: Project logging-log4j-tests (in module logging-log4j) 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 the folk at general <at> gump.apache.org.

Project logging-log4j-tests has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 13 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: 3 mins 18 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

(Continue reading)

headers

Leo Lima | 3 Oct 2006 16:15

Re: Enhanced FileAppender

Hello Bender.

> Problem:
> A often asked issue in user list is the problem to separate log files 
> dependent on different criterias, like a client-ID in a server 
> environment, a mandant- or task-ID in scheduler applications, etc. 
> Although it is possible to achieve this with the existing log4j framework 
> all possible solutions are quite complex  or have other drawbacks (own 
> repository selector, working with different classloaders, subclass 
> concrete descendents of FileAppender).

I used a KeyFileAppender I found for that porpouse. Take a look: 
http://mail-archives.apache.org/mod_mbox/logging-log4j-user/200305.mbox/%3C9C5166762F311146951505C6790A9CF858E97D <at> US-VS1.corp.mpi.com%3E
I've been using it for months now.

> Solution:
> The FileAppender is supplied with a property of type FileNameBuilder 
> (Design pattern: visitor). The user-supplied implementation of this 
> Interface can build a filename based on whatever criterias (i.e. MDC, 
> global Environment, etc.). The visitor is called each time a Fileappender 
> wants to append a log message. The FileAppender holds a collection of file 
> writers for each separate file name delivered by FileNameBuilder.
> To avoid the excess of open file handles the FileAppender could watch the 
> logging activity to one particular file. If the file was not accessed 
> after let's say one hour it could be closed (this timeout could also be 
> configurable). Special care must be done if the property "append" of the 
> FileAppender is false. If the file was closed because the above timeout 
> had elapsed and then reopened later again, the file shouldn't be 
> overridden.

(Continue reading)

headers

Bender Heri | 3 Oct 2006 17:51

RE: [SPAM (DNS Blacklist)] - Re: Enhanced FileAppender - Sending mail server found on sbl-xbl.spamhaus.org

OK, did not know yet about this KeyFileAppender. it's implementation is showing the direction of my
proposal, but...

1. my proposal is valid for all FileAppender's and its derivations (RollingFileAppender,
DailyRollingFileAppender) and not only for a specialized subclass (hence design pattern 'strategy')
2. KeyFileAppender supports only one MDC value, and this is only appended to the configured filename. With
my solution the app developper is free to build any filename (incl. different path) by using any arbitrary
values taken from where he/she likes.
3. A mechanism for garbage collecting no more used files is a must.

Some short hints to solve your problem of open files:

1. Each entry in your Writer Hashtable must have an additional field 'LastUse' of type Date which is updated
to the actual system time on each use of the Writer.
2. a separate thread checks periodically all writers if the field LastUse is older than a certain timeout
value (i.e. one hour). If so, it closes the writer.
3. Modifying access to this hashtable must be synchronized

Heri

> -----Original Message-----
> From: news [mailto:news <at> sea.gmane.org]On Behalf Of Leo Lima
> Sent: Tuesday, October 03, 2006 4:16 PM
> To: log4j-dev <at> logging.apache.org
> Subject: [SPAM (DNS Blacklist)] - Re: Enhanced FileAppender - Sending
> mail server found on sbl-xbl.spamhaus.org
> 
> 
> Hello Bender.
>

(Continue reading)

headers

Bender Heri | 3 Oct 2006 18:00

RE: Enhanced FileAppender

hi Wyssli

1. Maybe I cited the wrong desing pattern. You probably right that the strategy pattern would match cleaner
(it's an academic question).

2. It's also a good idea to provide the method buildFileName with the LoggingEvent. But the involved
appender should also be known (in order to get the configured filename).

3. I don't understand your proposal "closeFileAfter()" depending on the event. Who should call this? The
appender? The log4j user? I think a configurable timeout would be the way. See my response to Leo Lima some
minutes ago.

Heri

> -----Original Message-----
> From: patrick [mailto:Patrick.Wyss <at> mobilesolutions.ch]
> Sent: Tuesday, October 03, 2006 11:09 AM
> To: log4j-dev <at> logging.apache.org
> Subject: Re: Enhanced FileAppender
> 
> 
> 
> hi heri,
> 
> i like the idea a lot.
> however (admittedly without thinking to much about it ;-} ) i'd use
> "Strategy pattern" 
> http://www.dofactory.com/Patterns/PatternStrategy.aspx
> 
> and something like:

(Continue reading)

720	May 2013
490	April 2013
233	March 2013
179	February 2013
271	January 2013
164	December 2012
365	November 2012
328	October 2012
235	September 2012
126	August 2012
132	July 2012
107	June 2012
272	May 2012
66	April 2012
46	March 2012
28	February 2012
47	January 2012
15	December 2011
39	November 2011
144	October 2011
167	September 2011
149	August 2011
32	July 2011
58	June 2011
36	May 2011
44	April 2011
27	March 2011
53	February 2011
33	January 2011
31	December 2010
95	November 2010
74	October 2010
40	September 2010
30	August 2010
42	July 2010
95	June 2010
167	May 2010
54	April 2010
103	March 2010
116	February 2010
37	January 2010
42	December 2009
46	November 2009
138	October 2009
22	September 2009
43	August 2009
44	July 2009
28	June 2009
42	May 2009
25	April 2009
15	March 2009
35	February 2009
88	January 2009
79	December 2008
22	November 2008
57	October 2008
101	September 2008
353	August 2008
163	July 2008
157	June 2008
65	May 2008
26	April 2008
42	March 2008
49	February 2008
63	January 2008
49	December 2007
83	November 2007
111	October 2007
86	September 2007
373	August 2007
101	July 2007
317	June 2007
70	May 2007
363	April 2007
104	March 2007
124	February 2007
228	January 2007
58	December 2006
150	November 2006
52	October 2006
132	September 2006
148	August 2006
95	July 2006
35	June 2006
39	May 2006
59	April 2006
105	March 2006
212	February 2006
300	January 2006
233	December 2005
144	November 2005
116	October 2005
93	September 2005
185	August 2005
260	July 2005
120	June 2005
371	May 2005
128	April 2005
135	March 2005
304	February 2005
394	January 2005
568	December 2004
195	November 2004
99	October 2004
241	September 2004
125	August 2004
133	July 2004
222	June 2004
510	May 2004
184	April 2004
189	March 2004
90	February 2004
152	January 2004
442	December 2003
145	November 2003
172	October 2003
340	September 2003
136	August 2003
126	July 2003
492	June 2003
486	May 2003
207	April 2003
238	March 2003
417	February 2003
157	January 2003
200	December 2002
126	November 2002
179	October 2002
82	September 2002
65	August 2002
119	July 2002
247	June 2002
192	May 2002
77	April 2002
103	March 2002

Mon	Tue	Wed	Thu	Fri	Sat	Sun

						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30	31