db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5809) Log messages from the istat daemon doesn't include the database name/id
Date Wed, 26 Sep 2012 00:00:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-5809:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Log messages from the istat daemon doesn't include the database name/id
> -----------------------------------------------------------------------
>
>                 Key: DERBY-5809
>                 URL: https://issues.apache.org/jira/browse/DERBY-5809
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.8.2.2, 10.9.1.0, 10.10.0.0
>            Reporter: Kristian Waagan
>            Priority: Minor
>              Labels: derby_triage10_10
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message