You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/08/13 01:05:20 UTC

[jira] Commented: (GERONIMO-287) Control-C termination overwrites log files created with log4j.xml

The following comment has been added to this issue:

     Author: David Farb
    Created: Thu, 12 Aug 2004 4:04 PM
       Body:
Apparently if the Append parameter on the DailyRollingFileAppender is set to 'false' the above occurs. This implies that Geronimo is closing and re-opening the log while it is running. This close/open behavior seems to happen more often than just at termination.

The fix is to set:

        <param name="Append" value="true"/>

for the rolling file appender. Giving Geronimo a new file name for every invocation via command line properties creates a new log file for each invocation.

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/GERONIMO-287?page=comments#action_37234

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-287

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-287
    Summary: Control-C termination overwrites log files created with log4j.xml
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Apache Geronimo
 Components: 
             core

   Assignee: 
   Reporter: David Farb

    Created: Thu, 12 Aug 2004 10:59 AM
    Updated: Thu, 12 Aug 2004 4:04 PM
Environment: Windows 2000, Java 1.4.2_04, and Java 1.5.0-beta2, CVS of Aug 8, 2004

Description:
When running with a log4j.xml parameter file, and terminating Geronimo with a Control-C, the log files are overwritten starting with the time of termination. 

The final log only contains entries AFTER the control-C was issued, all the content prior to the Control-C is lost. 

Since Control-C is the only way to shut down at the moment, this is an issue to be aware of. 

If I get the chance, I will try to track it down, but ...




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira