axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Senaka Fernando (JIRA)" <>
Subject [jira] Commented: (AXIS2C-732) Log file size increasing with no upper limit
Date Thu, 25 Oct 2007 10:11:50 GMT


Senaka Fernando commented on AXIS2C-732:

Yes, this is a good improvement.
But, I have few suggestions to make it better.

1. We will not start from scratch, instead, the new file will have an entry saying that the
log file was backed up to the respective location, before starting with the logging procedure.
This well help the potential user of the log file identify what is going on.
2. Need to find mechanisms to handle situations such as, if log entries are needed to be made
during the process of backing up the log file. (Because, renaming and creating a new file
takes some time)
3. The user must be able to define the maximum size of the log file during installation. And,
this value must lie between a pre-defined range, or else the default must be assumed.


> Log file size increasing with no upper limit
> --------------------------------------------
>                 Key: AXIS2C-732
>                 URL:
>             Project: Axis2-C
>          Issue Type: Improvement
>            Reporter: Damitha Kumarage
> Currently log file size increase with no upper limit. In a production environment this
is not acceptable. To solve it I have provided a simple solution of after the file size exceeds
a certain limit it automatically is backed up to a x.log.old file and 
> log is written to from scratch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message