This is a feature of JBuilder Professional and Enterprise.
Use this dialog box to specify properties that control the behavior of the transaction manager for a transactional JDataStore.
Maximum number of log files that will be kept open at one time. Higher values may improve performance, but they will consume more system file handles.
Default is 2.
When a log file fills up to this size, a new log file (with the next number) is created and used. For example, after MyStore_LOGA_0000000000
reaches this size, MyStore_LOGA_0000000001
is created to record further transactions.
Default is 64 MB.
Frequency at which checkpoints are made to the log. checkFrequency is the amount of log file to be generated before starting a new checkpoint. A smaller value provides for faster crash recovery and faster-growing log files while a larger value provides for slower crash recovery and slower-growing log files.
Default is 2 MB.
Directory location of the primary copy of the log files, referred to as the "A" log files, and the STATUS
file, which collects status messages.
If left blank, the files are kept in the same directory as the JDataStore file.
Directory location of the secondary backup copy of the log files, referred to as the "B" log files.
Duplexing the log files will decrease performance, but increase the probability of a successful crash recovery. The only time log duplexing will benefit crash recovery is when there is media damage to the "A" log files or the "A" log files are lost, and the "B" log files are not damaged in the same locations or lost. Therefore, it's best to place the "B" log files on different media, preferably a different physical disk drive (which can also alleviate some of the performance penalty).
If left blank, no "B" log files will be generated.
Controls whether to use soft commit mode. Soft commit guarantees crash recovery for software application failures, but not from operating system and hardware failures. Soft commit mode improves performance by inhibiting the forced write of log files (the files are updated but might be cached in memory only and not written to disk), which makes the application more susceptible to system-level failures. Therefore, soft commit should be enabled only when operating system and hardware crash recovery is not critical or relevant.
By default, soft commit mode is disabled for greater reliability.
Controls whether various status messages will be recorded to the STATUS
log files, which are stored in the "A" log directory. Disabling this feature will improve performance slightly.
By default, this feature is enabled.