DO NOT REPLY [Bug 22038] New: - Appender truncates existing log files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22038>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22038

Appender truncates existing log files

           Summary: Appender truncates existing log files
           Product: Log4j
           Version: unspecified
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev <at> jakarta.apache.org
        ReportedBy: anderson.jb <at> ghc.org

Does FileAppender.setAppend("true") do anything? Each time we restart our app 
server, and log to a file, the existing file is truncated and the contents 
replaced with the new log statements. Although the documentation says appending 
is set to true by default. It would be appear otherwise. I've tried setting 
this via an XML config file and by calling setAppend() directing in the code. 
Same result either way.

[GUMP] Test Failure

----------------------------------------------------
This email is autogenerated from the output from:
<http://cvs.apache.org/builds/gump/2003-08-01/log4j-tests.html>
----------------------------------------------------

Buildfile: build.xml

parentBuild:
Caught exception (org.apache.tools.ant.BuildException) while expanding site2.classpath:
/home/rubys/jakarta/jakarta-log4j/${jakarta-site2}/lib not found.

init:

build.core:

oroCheck:

chainsawCheck:

build.chainsaw:

build.examples:

jaxpCheck:

jaxp:
     [echo] JAXP present.

build.xml:

DO NOT REPLY [Bug 22055] New: - Cannot catch PropertyConfigurator's IOException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22055>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22055

Cannot catch PropertyConfigurator's IOException

           Summary: Cannot catch PropertyConfigurator's IOException
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev <at> jakarta.apache.org
        ReportedBy: chet_p_d <at> hotmail.com

I have tried to search through all previously submitted bugs for 1.2 and FAQs 
but have not found an answer to the following, which I think maybe a bug:

public static void main(String[] args) {
Logger lg = Logger.getLogger(TestLog.class);
try{
PropertyConfigurator.configure("C:\\tmp\\LogProps.txt");
lg.debug("Done configuring logger");

Fw: [Apache Newsletter Draft] News on Jakarta in July, 2003

Dear Jakarta Log4j Development Team, 
(http://jakarta.apache.org/log4j/)

Hello,

I am now in the process of preparing the first all-Apache-wide newsletter.
http://www.apache.org/newsletter/

Please feel free to write statement/comment etc. to
the Apache Newsletter (Issue 1) using ApacheWiki
or in this mailing list. Hope to hear from you.
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1

Sincerely,

-- Tetsuya Kitahata (tetsuya <at> apache.org)

P.S. Jakarta Log4j Project's Wikipage is here:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages

Forwarded by Tetsuya Kitahata <tetsuya.kitahata <at> nifty.com>
----------------------- Original Message -----------------------
From:    Tetsuya Kitahata <tetsuya <at> apache.org>
To:      general <at> jakarta.apache.org
Date:    Fri, 01 Aug 2003 15:54:21 +0900
Subject: [Apache Newsletter Draft] News on Jakarta in July, 2003
----

Hello, All (Jakarta-General Mailing List Subscribers)

Bug report for Log4j [2003/08/03]

+---------------------------------------------------------------------------+
| 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                |
| 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res|
| 7678|Opn|Nor|2002-04-02|if log file is deleted, data will be lost until de|
| 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|
|10706|New|Enh|2002-07-11|MDC layout format %X{...} enhancement             |
|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|New|Nor|2002-08-03|Rolling, DailyRolling & FileAppender do not append|

Re: request for feedback on usage log management

Jeff Ubois wrote, On 05/08/2003 4.21:
> Hi,
> 
> The EFF is developing a Usage Log Management Tool (ULMT) 
...
> The UMLT is desgined to work with Apache servers, but also serves as a 
> reference implementation of policy recommendations by the EFF and the 
> working group.  The design documents are available at 
> http://www.eff.org/projects/logmanagement/, and suggestions for 
> improvement (as well as any feedback about whether this might be an 
> appropriate project for the incubator) would be much appreciated.

The Apache Jakarta Logj Project is thinking about proposing the creation 
of an Apache-wide project on logging, called logging.apache.org.

I suggest you to contact them on log4j-dev <at> jakarta.apache.org, and 
especially Ceki <ceki <at> qos.ch>, that is leading the effort.

--

-- 
Nicola Ken Barozzi                   nicolaken <at> apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------

FallbackErrorHandler loses the last event when switching to backup appender

LOGGING TLP (Re: request for feedback on usage log management)

I am wondering how it would be if the "i18n" TLP project (not yet
proposed) can tightly build up a closer connection with logging
TLP ... because all the commercial products have the error/log
messages in each native laguages (Oracle, MS, etc.)

-- Tetsuya (tetsuya <at> apache.org)

--

On Tue, 05 Aug 2003 08:39:57 +0200
(Subject: Re: request for feedback on usage log management)
Nicola Ken Barozzi <nicolaken <at> apache.org> wrote:

> 
> Jeff Ubois wrote, On 05/08/2003 4.21:
> > Hi,
> > 
> > The EFF is developing a Usage Log Management Tool (ULMT) 
> ...
> > The UMLT is desgined to work with Apache servers, but also serves as a 
> > reference implementation of policy recommendations by the EFF and the 
> > working group.  The design documents are available at 
> > http://www.eff.org/projects/logmanagement/, and suggestions for 
> > improvement (as well as any feedback about whether this might be an 
> > appropriate project for the incubator) would be much appreciated.
> 
> The Apache Jakarta Logj Project is thinking about proposing the creation 
> of an Apache-wide project on logging, called logging.apache.org.
> 
> I suggest you to contact them on log4j-dev <at> jakarta.apache.org, and 
> especially Ceki <ceki <at> qos.ch>, that is leading the effort.
> 
> -- 
> Nicola Ken Barozzi                   nicolaken <at> apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------

-----------------------------------------------------
Tetsuya Kitahata --  Terra-International, Inc.
E-mail: tetsuya <at> apache.org
http://www.terra-intl.com/
(Apache Jakarta Translation, Japanese)
http://jakarta.terra-intl.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe <at> incubator.apache.org
For additional commands, e-mail: general-help <at> incubator.apache.org

Nicola Ken Barozzi suggested getting in touch re: usage log management

Hi,

I posted a note to general <at> incubator.apache.org,  and got a reply 
suggested I get in touch with this list, and with Ceki.  My original
post is below.  If this is interesting to you, I also have a draft 
policy document that came out of the working group meeting.

Best,
Jeff

======

Date: Tue, 05 Aug 2003 08:39:57 +0200
To: general <at> incubator.apache.org
From: Nicola Ken Barozzi <nicolaken <at> apache.org>
Cc: log4j-dev <at> jakarta.apache.org
Subject: Re: request for feedback on usage log management
Message-ID: <bgnjir$aal$1 <at> main.gmane.org>

Jeff Ubois wrote, On 05/08/2003 4.21:

>> Hi,
>> 
>> The EFF is developing a Usage Log Management Tool (ULMT) 
>  
>
...

>> The UMLT is desgined to work with Apache servers, but also serves as a 
>> reference implementation of policy recommendations by the EFF and the 
>> working group.  The design documents are available at 
>> http://www.eff.org/projects/logmanagement/, and suggestions for 
>> improvement (as well as any feedback about whether this might be an 
>> appropriate project for the incubator) would be much appreciated.
>  
>

The Apache Jakarta Logj Project is thinking about proposing the creation 
of an Apache-wide project on logging, called logging.apache.org.

I suggest you to contact them on log4j-dev <at> jakarta.apache.org, and 
especially Ceki <ceki <at> qos.ch>, that is leading the effort.

-- nicolaken <at> apache.org - verba volant, scripta manent - (discussions 
get forgotten, just code remains) === Hi, The EFF is developing a Usage 
Log Management Tool (ULMT) that will help web site owners manage the 
configuration and retention of server logs in ways that help ensure end 
user privacy and reduce legal risks associated with log file data. The 
design is based on ideas developed at the Usage Log Data Management 
Working Group (see 
http://www.cfp2003.org/cfp2003/program_info/usage_log_working_group.html) 
at the Computers, Freedom, and Privacy Conference in New York City in 
April.  Background on that meeting is available at 
http://www.securityfocus.com/news/3711. The UMLT is desgined to work 
with Apache servers, but also serves as a reference implementation of 
policy recommendations by the EFF and the working group.  The design 
documents are available at http://www.eff.org/projects/logmanagement/, 
and suggestions for improvement (as well as any feedback about whether 
this might be an appropriate project for the incubator) would be much 
appreciated. Thanks, Sverker Hogberg Dan Moniz Jeff Ubois

Re: LOGGING TLP (Re: request for feedback on usage log management)

Tetsuya,

 From an architectural perspective, I think the logging component should 
delegate i8n support to a specialized component. So it makes sense for 
log4j to rely on  "i18n" TLP project although more information on the 
"i18n" project is needed to pursue the discussion.

Where can I find more about this project?

At 09:41 AM 8/6/2003 +0900, Tetsuya Kitahata wrote:

>I am wondering how it would be if the "i18n" TLP project (not yet
>proposed) can tightly build up a closer connection with logging
>TLP ... because all the commercial products have the error/log
>messages in each native laguages (Oracle, MS, etc.)
>
>-- Tetsuya (tetsuya <at> apache.org)

Ceki For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp