Derby
  1. Derby
  2. DERBY-4853

log derby.properties location and derby.log location to derby.log

    Details

    • Urgency:
      Normal

      Description

      Often when a Derby issue occurs, the derby.log is the one thing that does get retrieved, but often gets passed through many layers before it reaches the people supporting Derby. It would be helpful if derby.log also included the following to help instruct customers how to change derby.properties or look again at the log.
      1) derby.properties location.
      2) derby.log location or indicate how error log redirection is defined.

        Issue Links

          Activity

          Hide
          Mamta A. Satoor added a comment -

          I will take a look at this to see what work is involved

          Show
          Mamta A. Satoor added a comment - I will take a look at this to see what work is involved
          Hide
          Mamta A. Satoor added a comment -

          It will be useful to know in derby.log, the possible locations of derby.properties and derby.log. Following 2 additional properties will now always be put in derby.log (every time a database is booted. Similar to existing jvminfo that is printed in derby.log)
          user.dir
          derby.system.home

          user.dir is the system property which gives the user working directory. If the user has not specified derby,system.home, then Derby will look for optional derby.properties file in user.dir . If user has provided derby.system.home, then the optional derby.properties will be looked in derby.system.home rather than user.dir

          If user has not provided derby.system.home, then a sample of the 2 properties on derby.log looks as follows on my machine
          user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142
          derby.system.home=null

          If user has set derby.system.home to c:./temp, then a sample of the 2 properties on derby.log looks as follows on my machine
          user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142
          derby.system.home=c:/temp

          In addition to the above 2 properties, there can be following 3 optional properties in the log (following the 2 properties mentioned above)
          derby.stream.error.file
          derby.stream.error.method
          derby.stream.error.field

          The above 3 properties provide a way to alter where error messages get logged rather than tranditional derby.log file. In the absence of the above 3 optional properties, the location of derby.log follows the same logic as derby.properties. But if the user has set any or all of the 3 optional properties, then derby.log will not be in same location as derby.properties. In the Derby code, derby.stream.error.file takes precedence over the other 2 properties and derby.stream.error.method take precedence over the last property.

          Hopefully this additional information in the log file will be handy when working with customer issues. I have attached the patch for the code changes to accomplish above logging enhancement.

          Show
          Mamta A. Satoor added a comment - It will be useful to know in derby.log, the possible locations of derby.properties and derby.log. Following 2 additional properties will now always be put in derby.log (every time a database is booted. Similar to existing jvminfo that is printed in derby.log) user.dir derby.system.home user.dir is the system property which gives the user working directory. If the user has not specified derby,system.home, then Derby will look for optional derby.properties file in user.dir . If user has provided derby.system.home, then the optional derby.properties will be looked in derby.system.home rather than user.dir If user has not provided derby.system.home, then a sample of the 2 properties on derby.log looks as follows on my machine user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 derby.system.home=null If user has set derby.system.home to c:./temp, then a sample of the 2 properties on derby.log looks as follows on my machine user.dir=C:\p4clients\svnmain\client2\trunk\systest\out142 derby.system.home=c:/temp In addition to the above 2 properties, there can be following 3 optional properties in the log (following the 2 properties mentioned above) derby.stream.error.file derby.stream.error.method derby.stream.error.field The above 3 properties provide a way to alter where error messages get logged rather than tranditional derby.log file. In the absence of the above 3 optional properties, the location of derby.log follows the same logic as derby.properties. But if the user has set any or all of the 3 optional properties, then derby.log will not be in same location as derby.properties. In the Derby code, derby.stream.error.file takes precedence over the other 2 properties and derby.stream.error.method take precedence over the last property. Hopefully this additional information in the log file will be handy when working with customer issues. I have attached the patch for the code changes to accomplish above logging enhancement.
          Hide
          Mike Matrigali added a comment -

          10.8 triage. looks like a feature not a bug to me. would be nice to get this one in for supportability.

          Show
          Mike Matrigali added a comment - 10.8 triage. looks like a feature not a bug to me. would be nice to get this one in for supportability.
          Hide
          Kathey Marsden added a comment -

          Finished backporting to 10.5. For 10.5 there was a comment error so it does not show on the subversion commits the 10.5 change was revision 1083351

          Show
          Kathey Marsden added a comment - Finished backporting to 10.5. For 10.5 there was a comment error so it does not show on the subversion commits the 10.5 change was revision 1083351
          Hide
          Knut Anders Hatlen added a comment -

          [bulk update] Close all resolved issues that haven't been updated for more than one year.

          Show
          Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.

            People

            • Assignee:
              Mamta A. Satoor
              Reporter:
              Kathey Marsden
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development