Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6350

Provide a rolling file implementation of derby.log



    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s:
    • Component/s: Miscellaneous
    • Labels:


      By default, derby.log grows without bounds if the derby.infolog.append property is set to "true". Setting this to "true" helps in a hands off production environment to ensure that if Derby restarts, the derby.log which might contain important information is not lost. On the other hand, when set the "true" the derby.log grows without bounds. This is problematic in a long running system.

      What is really needed is the ability to have a rolling derby.log file support where the maximum file size and maximum number of files can be specified. Derby has the ability to configure the location of the log file (ie. derby.stream.error.file) and also two methods of redirecting the error stream (.ie derby.stream.error.method and derby.stream.error.field). There is no standard implementation that supports a rolling derby.log however.

      This facility should be part of the core Derby system so that it works in both embedded and network server models.


        1. ErrorStreamTest_rolling_file_cleanup.patch
          0.9 kB
          Brett Bergquist
        2. rolling_file_patch_7.diff
          44 kB
          Brett Bergquist
        3. rolling_file_patch_6.txt
          44 kB
          Brett Bergquist
        4. rolling_file_patch_5.txt
          43 kB
          Brett Bergquist
        5. rollingfilelog.patch.txt
          31 kB
          Brett Bergquist
        6. rollingfilelog.patch.txt
          28 kB
          Brett Bergquist

          Issue Links



              • Assignee:
                bbergquist Brett Bergquist
                bbergquist Brett Bergquist
              • Votes:
                0 Vote for this issue
                11 Start watching this issue


                • Created: