db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0
Date Wed, 16 Jun 2010 16:54:22 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879380#action_12879380

Kathey Marsden commented on DERBY-1272:

I have been thinking about this issue, perhaps the full sysinfo is just overkill for derby.log,
especially considering all the extra permissions that are required. The critical information
that is routinely needed in derby.log that is not there already is the jvm version and if
possible the derby.jar location (not sure how to do this).  Maybe we should try to print just
this information compactly to derby.log and not go for the full sysinfo.

> Change sysinfo to print to error log (derby.log) on boot of derby  if derby.stream.error.logSeverityLevel=0
> -----------------------------------------------------------------------------------------------------------
>                 Key: DERBY-1272
>                 URL: https://issues.apache.org/jira/browse/DERBY-1272
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions:,,
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: derby-1272-pre.diff, derby-1272-pre2.diff, derby-1272-pre3.diff,
derby-1272-v4.diff, DERBY-1272v5.diff, DERBY-1272v6.diff, DERBY-1272v6.stat, DERBY-1272v8.diff
> It is often very difficult to collect correct sysinfo output from user environments because
 sysinfo run from the commandline does not have the same classpath as the jvm that started
Derby or Derby was loaded with a custom classloader.
> It would be very helpful in assisting users in diagnosing their issues if sysinfo dumped
to the error log if  derby.stream.error.logSeverityLevel=0  or even by default.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message