db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Watzek <mwa.t...@spree.de>
Subject TCK logging proposal
Date Tue, 16 Aug 2005 15:31:34 GMT

during last t-conference we discussed to improve logging of TCK runs. 
Below, you find a summary of our discussion. Please comment!

Current state:
Separate log files are written by JPOX, JPOX enhancer, Derby, and TCK. 
The locations of these log files are:

- JPOX: "target/jpox.log".
- JPOX enhancer: "target/enhanced/<identity type>/jpox.log"
- Derby: "target/database/derby/derby.log
- TCK: "target/logs/<timestamp>-<database>-<identity 

The current logging configuration determines that JPOX and JPOX enhancer 
append output to log files. Derby truncates the log file for each TCK 
configuration. In contrast, the TCK writes a new log file for each TCK 
configuration result.

Each component writes to a different log directory. The directories are 
not under a common root. This fact complicates the log analysis. On the 
other hand, the TCK writes a separate log file for each configuration 
result to directory "target/logs". Currently, there are 14 different 
configurations. There will be approximately 22 when the inheritance 
proposal is implemented. Thus, each TCK run will produce 22 new files in 
directory "target/logs". Obviously, this  fact reduces facility of 

The proposal is to have separate log directories for each TCK run. These 
log directories are located under the common parent directory 
"target/logs". The naming pattern for these directories are given by 
timestamp format "yyyyMMdd-HHmmss". The directory contents are:

- Separate log file for each TCK configuration result. The naming 
pattern is: "<database>-<identity type>-<configuration>.txt".
- Separate JPOX log file for each TCK configuration. The naming pattern 
is: "<database>-<identity type>-<configuration>-jpox.txt".

Thus, each TCK run will produce 44 files in separate log directories.

The proposal is to write the JPOX enhancer log to directory 
"target/logs/enhancer". There, separate files will be written for each 
identity type. Successive enhancer runs append the log to these files. 
The file name pattern is "<identity type>-jpox.txt".

The proposal is to write the database log to directory 
"target/logs/database". There, a common file for all identity types and 
configurations will be written. Each run will append the log to that 
file. The file name pattern is "<database>.txt"

The log level of all components is "INFO".

Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/

View raw message