detail.php
OW2 Forge: Detail: 300830 Ignore bufferSize conflicts between existing log files and configuration

Advanced - Powered by Google


   
Log In
New Account
  
 
Home
My Page
Project Tree
Project Openings
High-speed ObjectWeb Logger
          
 
 
Summary
Tracker
Lists
Tasks
News
CVS
Files
SVN
                
 

Tracker: Feature Requests

Submit New | Browse | Admin | ExportToXml

[ #300830 ] Ignore bufferSize conflicts between existing log files and configuration

Date:
2004-09-21 00:47
Priority:
5
Submitted By:
Michael Giroux (girouxm)
Assigned To:
Nobody (None)
Category:
None
State:
Open
Summary:
Ignore bufferSize conflicts between existing log files and configuration

Detailed description:
The current Logger code will throw an exception during Logger.open() if a) the log files already exist and b) the block size is not the same as the configuration This might happen if the administrator modified the configuration before doing an application restart. It has been suggested that in this case, HOWL could restart using the existing file block size, and ignore the bufferSize configuration setting. If the administrator actually desired to establish a new block size, then they could delete existing log files. I like the suggestion, but would like some discussion on the possible implementation. I can think of a couple of options, and there may be others. 1. if log files already exist, then always restart using the original block size ignoring the configured bufferSize setting. This action probably should result in an event log message when HOWL supports an event log. 2. make the new feature optional by adding a new parameter that indicates whether or not to use existing block size. ignoreBufferSizeException = true/false -- default false The second option preserves existing mode of operation while allowing for the new approach. Comments and other suggestions appreciated.

Add A Comment:

Please login

Followup

Message
Date: 2004-11-05 21:12
Sender: girouxm
Logged In: YES 
user_id=343

I think this feature could be supported for cases when the
Logger is constructed with a default Configuration.  In this
case, all configuration information could be retrieved from
the existing journal files.

If an application specifies a Configuration.properties file,
then it seems to me that the explicit configuration should
be enforced.

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

No Changes Have Been Made to This Item

Copyright © 1999-2008, OW2 Consortium | contact | You have a difficulty, a problem ? Please report an issue using your OW2 forge account credentials