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

Log messages from the istat daemon doesn't include the database name/id

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.8.2.2, 10.9.1.0, 10.10.1.1
    • Fix Version/s: None
    • Component/s: Services
    • Urgency:
      Normal
    • Issue & fix info:
      Newcomer

      Description

      When the istat daemon emits log messages only a partial header is prepended. This means that in systems with many databases it may be impossible to tell which database the message belongs to.

      A workaround is to enable tracing, but that results in increased log volume. Most of the additional information is of no use during normal operation.
      Another way to identify the database is to look at the table names or table identifiers.

      The correct fix is probably to include the database in the log message header, which is what's done for many/most other messages in derby.log.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kristwaa Kristian Waagan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: